home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The World of Computer Software
/
The World of Computer Software.iso
/
0rm200-4.zip
/
SYSGUIDE.TXT
Wrap
Text File
|
1993-02-08
|
445KB
|
10,220 lines
Sysop's Guide to RoseMail
Wide Beta Version
Sun 7 Feb 1993, 17:40
Written for the RoseMail Team:
Developers and Sysops
by Carol Whitney
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page ii
CONTENTS
PREFACE (wide beta). . . . . . . . . . . . . . . . . . . . . .xiii
ACKNOWLEDGMENTS: Sysop's Guide To RoseMail. . . . xiv
INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . 1
ROSEREADER FOR SYSOPS. . . . . . . . . . . . . . . . . . . . . 2
ABOUT THIS GUIDE . . . . . . . . . . . . . . . . . . . . . . . 3
SYSTEM REQUIREMENTS FOR RUNNING ROSEMAIL . . . . . . . . . . . 4
GUIDED TOUR. . . . . . . . . . . . . . . . . . . . . . . . . . 4
The PCBoard-RoseMail Link. . . . . . . . . . . . . . . . . . 5
Netmail software in RoseMail . . . . . . . . . . . . . . . 5
RoseNet registered, routed mail. . . . . . . . . . . . . . 6
Installing RoseMail with PCBoard . . . . . . . . . . . . . 7
What is a node?. . . . . . . . . . . . . . . . . . . . . . . 8
Node directory . . . . . . . . . . . . . . . . . . . . . . 8
RoseMail makes the node directory the current directory. . 10
ROSEMAIL, the "KEYWORD" file . . . . . . . . . . . . . . . 11
What happens to the KEYWORD file ROSEMAIL . . . . . . . 12
Tour of RoseMail operations. . . . . . . . . . . . . . . . . 13
RoseMail's configuration file: RMAIL.DAT. . . . . . . . . . 15
Special RoseMail configurations for individual nodes . . . . 16
The RoseMail Work Directory. . . . . . . . . . . . . . . . . 18
ROSENET MAIL . . . . . . . . . . . . . . . . . . . . . . . . . 19
Introduction to RoseNet. . . . . . . . . . . . . . . . . . . 19
RoseNet Features . . . . . . . . . . . . . . . . . . . . . . 20
Range for RoseNet messages . . . . . . . . . . . . . . . . 20
RoseNet Message features . . . . . . . . . . . . . . . . . 21
Registration of software via RoseNet . . . . . . . . . . . 22
QUICK-INSTALL. . . . . . . . . . . . . . . . . . . . . . . . . 27
How to Use Quick-Install . . . . . . . . . . . . . . . . . . 27
Steps to perform for a quick installation. . . . . . . . . . 28
BACKUP: Back up your system!. . . . . . . . . . . . . . . 28
SYSTEM CONFIGURATION: Check your CONFIG.SYS file. . . . . 28
SUBDIRECTORIES: Make subdirectories to hold RoseMail
files.. . . . . . . . . . . . . . . . . . . . . . . . . 28
EXTERNAL PROTOCOLS . . . . . . . . . . . . . . . . . . . . 29
Choose DOOR NUMBER and SECURITY LEVEL. . . . . . . . . . . 29
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page iii
COPY FILES . . . . . . . . . . . . . . . . . . . . . . . . 30
PCBSM: PCBoard System Manager.. . . . . . . . . . . . . . 31
RM.EXE: The RoseMail System Manager.. . . . . . . . . . . 35
NOTES on File Paths for PCBOARD.DAT, PCBOARD.SYS & USERS.SYS 35
MULTI-NODE SYSTEMS: Checking a global RoseMail
installation. . . . . . . . . . . . . . . . . . . . . . 41
ROSEMAIL MAIN REFERENCE. . . . . . . . . . . . . . . . . . . . 42
GENERAL INFORMATION. . . . . . . . . . . . . . . . . . . . . . 42
What you need to know. . . . . . . . . . . . . . . . . . . . 42
Assumed: You know DOS . . . . . . . . . . . . . . . . . . 42
Assumed: You know your network software . . . . . . . . . 42
Assumed: You know the PCBoard software. . . . . . . . . . 42
CONVENTIONS used in these instructions . . . . . . . . . . . 43
Exceptions to flexibility in directory names . . . . . . . . 43
Terminology used in this guide . . . . . . . . . . . . . . . 44
BBS.QWK and BBS.REP. . . . . . . . . . . . . . . . . . . . 44
HUB.QWK and HUB.REP. . . . . . . . . . . . . . . . . . . . 44
Screen simulations . . . . . . . . . . . . . . . . . . . . . 44
ORIENTATION to the task. . . . . . . . . . . . . . . . . . . 45
INSTALLING ROSEMAIL. . . . . . . . . . 46
Initial steps to take. . . . . . . . . . . . . . . . . . . . 46
BACKUP . . . . . . . . . . . . . . . . . . . . . . . . . . 46
SYSTEM CONFIGURATION . . . . . . . . . . . . . . . . . . . 46
SUBDIRECTORIES . . . . . . . . . . . . . . . . . . . . . . 47
EXTERNAL PROTOCOLS . . . . . . . . . . . . . . . . . . . . 48
Choose DOOR NUMBER and SECURITY LEVEL. . . . . . . . . . . 49
COPY FILES . . . . . . . . . . . . . . . . . . . . . . . . 50
PCBSM: PCBoard System Manager.. . . . . . . . . . . . . . 51
THE ROSEMAIL SYSTEM MANAGER. . . . . . . . 57
GENERAL INFORMATION. . . . . . . . . . . . . . . . . . . . . . 57
Planning Your System . . . . . . . . . . . . . . . . . . . . 57
Planning the location of the configuration file RMAIL.DAT. 58
RoseMail System Manager: List of Editing Keys . . . . . . . 59
List of editing functions. . . . . . . . . . . . . . . . . . 61
Select a Submenu . . . . . . . . . . . . . . . . . . . . . 61
Leave a Submenu. . . . . . . . . . . . . . . . . . . . . . 61
Scroll Screen. . . . . . . . . . . . . . . . . . . . . . . 61
Move to Next Field . . . . . . . . . . . . . . . . . . . . 61
Move to Previous Field . . . . . . . . . . . . . . . . . . 61
Move to Beginning of Field . . . . . . . . . . . . . . . . 62
Move to End of Field . . . . . . . . . . . . . . . . . . . 62
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page iv
Toggle Insert Mode . . . . . . . . . . . . . . . . . . . . 62
Edit information in a field (edit what is already there) . 62
Edit information in a field (erase what is already there). 62
Restore previous information in a field. . . . . . . . . . 63
Delete all information in a field. . . . . . . . . . . . . 63
Exit without saving your configuration . . . . . . . . . . 63
Save your configuration. . . . . . . . . . . . . . . . . . 63
Flag-setting keys: set or clear multiple flags. . . . . . 63
Ask for and jump to a specified conference number . . . 64
Set flags for a range of conferences. . . . . . . . . . 64
Clear flags for a range of conferences. . . . . . . . . 64
CONFIGURING WITH THE ROSEMAIL SYSTEM MANAGER. . . . 64
Orientation to configuring RoseMail. . . . . . . . . . . . . 65
To configure RoseMail for the first time . . . . . . . . . 65
RM.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Finding your way around the menus. . . . . . . . . . . . . 65
Context-sensitive help . . . . . . . . . . . . . . . . . . 65
THE ROSEMAIL SYSTEM MANAGER'S MAIN MENU. . . . . 66
DESCRIPTION OF SUBMENUS. . . . . . . . . . . . . . . . . . . . 66
File Paths . . . . . . . . . . . . . . . . . . . . . . . . . 67
Compression Programs . . . . . . . . . . . . . . . . . . . . 67
Transfer Protocols . . . . . . . . . . . . . . . . . . . . . 67
Transfer rates/limits. . . . . . . . . . . . . . . . . . . . 67
Local board information. . . . . . . . . . . . . . . . . . . 67
Duplicate checks . . . . . . . . . . . . . . . . . . . . . . 67
Options. . . . . . . . . . . . . . . . . . . . . . . . . . . 68
RoseNet Information. . . . . . . . . . . . . . . . . . . . . 68
Networks/NetMail . . . . . . . . . . . . . . . . . . . . . . 68
Conference data. . . . . . . . . . . . . . . . . . . . . . . 68
User Flags . . . . . . . . . . . . . . . . . . . . . . . . . 68
Add In Files . . . . . . . . . . . . . . . . . . . . . . . . 69
Magazines. . . . . . . . . . . . . . . . . . . . . . . . . . 69
Conference Optimize. . . . . . . . . . . . . . . . . . . . . 69
THE ROSEMAIL SYSTEM MANAGER: SUBMENUS . . . . . . . . . . . . 70
FILE PATHS . . . . . . . . . . . . . . . . . . . . . . . . . . 70
ASCII Editor . . . . . . . . . . . . . . . . . . . . . . . . 71
ANSI Editor. . . . . . . . . . . . . . . . . . . . . . . . . 72
Editing the Help Files . . . . . . . . . . . . . . . . . . . 72
Rmail Directory. . . . . . . . . . . . . . . . . . . . . . . 72
CONFDATA.DAT . . . . . . . . . . . . . . . . . . . . . . . . 73
Other File Paths . . . . . . . . . . . . . . . . . . . . . . 73
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page v
Note for single-node sysops. . . . . . . . . . . . . . . . 73
Note for multi-node sysops . . . . . . . . . . . . . . . . 74
PCBOARD.DAT. . . . . . . . . . . . . . . . . . . . . . . . . 74
PCBOARD.SYS. . . . . . . . . . . . . . . . . . . . . . . . . 75
USERS.SYS. . . . . . . . . . . . . . . . . . . . . . . . . . 75
Work Directory . . . . . . . . . . . . . . . . . . . . . . . 75
USING DOS ENVIRONMENT VARIABLES IN FILE PATHS. . . . . . . . . 76
PCBoard 14.5a DOS environment variables. . . . . . . . . . . 76
DOS environment variables in File Paths. . . . . . . . . . 76
Examples of File Path configuration. . . . . . . . . . . . 77
Example BOARD.BAT for NODE 2. . . . . . . . . . . . . . 79
The #-variable in File Paths . . . . . . . . . . . . . . . 80
The #-variable and the PCBNODE variable. . . . . . . . . . . 81
Adding the /n switch . . . . . . . . . . . . . . . . . . . 82
Summary of "#" or "%PCBNODE%" recommendations. . . . . . . 83
COMPRESSION PROGRAMS . . . . . . . . . . . . . . . . . . . . . 84
Letter . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Compression program (executable filename). . . . . . . . . . 85
Decompression program (executable filename). . . . . . . . . 86
Adding extra configurations for the same compression
program . . . . . . . . . . . . . . . . . . . . . . . . 86
TRANSFER PROTOCOLS . . . . . . . . . . . . . . . . . . . . . . 88
General Information. . . . . . . . . . . . . . . . . . . . . 88
Orientation to the Transfer Protocol screens . . . . . . . . 89
Let. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Err. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Bat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Download program . . . . . . . . . . . . . . . . . . . . . . 91
Upload program . . . . . . . . . . . . . . . . . . . . . . . 92
Environment variable (DSZLOG). . . . . . . . . . . . . . . . 93
INTERNAL PROTOCOLS . . . . . . . . . . . . . . . . . . . . . 93
CHECKLIST FOR CONFIGURING EXTERNAL TRANSFER PROTOCOLS. . . . . 95
Define Transfer Protocols. . . . . . . . . . . . . . . . . . 95
Tell RoseMail how to find DSZ. . . . . . . . . . . . . . . 96
Configure the DSZ command lines (optional) . . . . . . . . 96
Point to DSZ using the Transfer Protocol command lines . . 96
Check the DSZ command lines. . . . . . . . . . . . . . . . 97
Edit the DSZ command lines . . . . . . . . . . . . . . . . 97
Other alterations you may make to command lines. . . . . . 98
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page vi
Installing other protocol programs . . . . . . . . . . . . 99
Examples of command lines for other protocols . . . . . 99
Xmodem-1K from DSZ. . . . . . . . . . . . . . . . . . 99
HS/Link by Samuel Smith . . . . . . . . . . . . . . . 99
TRANSFER RATES/LIMITS. . . . . . . . . . . . . . . . . . . . . 100
Transfer Rate. . . . . . . . . . . . . . . . . . . . . . . . 101
Max msgs/conf. . . . . . . . . . . . . . . . . . . . . . . . 101
Max msgs/packet. . . . . . . . . . . . . . . . . . . . . . . 101
Setting a limit on number of messages per conference . . . . 101
Setting a limit on number of messages per .QWK packet. . . . 102
Caller's SIZ command . . . . . . . . . . . . . . . . . . . . 102
Caller may set limit on expanded packet size . . . . . . . 102
Caller Repeat Downloads. . . . . . . . . . . . . . . . . . . 103
LOCAL BOARD INFORMATION. . . . . . . . . . . . . . . . . . . . 103
Board Information. . . . . . . . . . . . . . . . . . . . . . 103
Board name . . . . . . . . . . . . . . . . . . . . . . . . . 104
Sysop name . . . . . . . . . . . . . . . . . . . . . . . . . 105
Board telephone. . . . . . . . . . . . . . . . . . . . . . . 105
Packet name. . . . . . . . . . . . . . . . . . . . . . . . . 105
Local directory. . . . . . . . . . . . . . . . . . . . . . . 105
Network QWK dir. . . . . . . . . . . . . . . . . . . . . . . 106
Network REP dir. . . . . . . . . . . . . . . . . . . . . . . 106
Trashcan file. . . . . . . . . . . . . . . . . . . . . . . . 106
DUPLICATE CHECKING . . . . . . . . . . . . . . . . . . . . . . 107
Door dupe block. . . . . . . . . . . . . . . . . . . . . . . 109
RM dupe block. . . . . . . . . . . . . . . . . . . . . . . . 109
RoseNet # of messages. . . . . . . . . . . . . . . . . . . . 110
Start conference . . . . . . . . . . . . . . . . . . . . . . 110
Stop conference. . . . . . . . . . . . . . . . . . . . . . . 110
Start RDX rebuild. . . . . . . . . . . . . . . . . . . . . . 110
OPTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Remove REP file. . . . . . . . . . . . . . . . . . . . . . . 112
Remove QWK file. . . . . . . . . . . . . . . . . . . . . . . 112
Remove local REP . . . . . . . . . . . . . . . . . . . . . . 113
Net Sysop Backup . . . . . . . . . . . . . . . . . . . . . . 113
Mark SysOp read. . . . . . . . . . . . . . . . . . . . . . . 113
Set Mail Waiting . . . . . . . . . . . . . . . . . . . . . . 113
Ignore Echo Flag . . . . . . . . . . . . . . . . . . . . . . 114
Swap to XMS. . . . . . . . . . . . . . . . . . . . . . . . . 115
Swap to EMS. . . . . . . . . . . . . . . . . . . . . . . . . 115
Swap to Disk . . . . . . . . . . . . . . . . . . . . . . . . 115
Tip on Swapping Techniques . . . . . . . . . . . . . . . . . 115
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page vii
Max Carbon Copy. . . . . . . . . . . . . . . . . . . . . . . 116
File Downloads . . . . . . . . . . . . . . . . . . . . . . . 116
File Uploads . . . . . . . . . . . . . . . . . . . . . . . . 116
Prescan Security . . . . . . . . . . . . . . . . . . . . . . 116
Max prescan (K). . . . . . . . . . . . . . . . . . . . . . . 117
Max Work Size (K). . . . . . . . . . . . . . . . . . . . . . 117
ROSENET INFORMATION. . . . . . . . . . . . . . . . . . . . . . 117
NETWORKS/NETMAIL . . . . . . . . . . . . . . . . . . . . . . . 121
General Information. . . . . . . . . . . . . . . . . . . . . 121
Arranging to carry netmail . . . . . . . . . . . . . . . . . 121
How RoseMail handles netmail . . . . . . . . . . . . . . . . 122
RoseMail Echo Mail Features. . . . . . . . . . . . . . . . . 122
Public echo mail . . . . . . . . . . . . . . . . . . . . . 122
Echo flag . . . . . . . . . . . . . . . . . . . . . . . 123
Control which messages in a conference shall be echoed . . 123
Personal Echo Mail. . . . . . . . . . . . . . . . . . . 124
CONFIGURING NETWORKS/NETMAIL . . . . . . . . . . . . . . . . 124
Special care needed with numbers . . . . . . . . . . . . . 124
The Networks/NetMail Menu. . . . . . . . . . . . . . . . . 125
HOW TO CONFIGURE AVAILABLE NETWORKS. . . . . . . . . . . . . 127
Available Networks . . . . . . . . . . . . . . . . . . . . 127
Network number. . . . . . . . . . . . . . . . . . . . . 128
Network name. . . . . . . . . . . . . . . . . . . . . . 129
Packet. . . . . . . . . . . . . . . . . . . . . . . . . 129
Pre-defined nets. . . . . . . . . . . . . . . . . . . . 130
Defining your own networks. . . . . . . . . . . . . . . 133
CONFERENCE OWNERSHIP . . . . . . . . . . . . . . . . . . . . 134
NET SYSOP ACCESS . . . . . . . . . . . . . . . . . . . . . . 136
Net Sysop Address. . . . . . . . . . . . . . . . . . . . . 136
NETWORK TRANSLATIONS . . . . . . . . . . . . . . . . . . . . 137
Translation. . . . . . . . . . . . . . . . . . . . . . . . 140
Last read. . . . . . . . . . . . . . . . . . . . . . . . . 140
Highest in base. . . . . . . . . . . . . . . . . . . . . . 141
Network Translations: change networks . . . . . . . . . . . 141
TAGLINES . . . . . . . . . . . . . . . . . . . . . . . . . . 141
POINTER RESETS . . . . . . . . . . . . . . . . . . . . . . . 142
USERS.INF RESET. . . . . . . . . . . . . . . . . . . . . . . 144
CONFERENCE DATA. . . . . . . . . . . . . . . . . . . . . . . . 145
Flag 1: Force this conference to be scanned . . . . . . . . 147
Flag 2: Insert all messages as personal . . . . . . . . . . 147
Flag 3: Insert all messages as public . . . . . . . . . . . 147
Flag 4: Deny all insertion attempts . . . . . . . . . . . . 147
Flag 5: Allow personal echo mail. . . . . . . . . . . . . . 147
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page viii
Flag 6: Include new bulletins . . . . . . . . . . . . . . . 147
Flag 7: Include upload file listings. . . . . . . . . . . . 148
Flag 8: Continue file scans past "old" files. . . . . . . . 148
Flag 9: Include the NEWS file . . . . . . . . . . . . . . . 148
Flag 10: Force the NEWS file. . . . . . . . . . . . . . . . 148
Flag 11: Include download file listings . . . . . . . . . . 148
Flag 12: Allow aliases. . . . . . . . . . . . . . . . . . . 149
Flag 13: Ignore PCBoard private flag. . . . . . . . . . . . 149
Flag 14: Force echo flag on . . . . . . . . . . . . . . . . 149
Flag 15: Force message date/time to time of insertion.. . . 149
Flag 16: Force this conference to be scanned (Personal or
All) . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
Flag 17: Strip ANSI codes in incoming messages. . . . . . . 149
USER FLAGS . . . . . . . . . . . . . . . . . . . . . . . . . . 150
Flag 1: Scan for personal messages. . . . . . . . . . . . . 151
Flag 2: Scan for public messages. . . . . . . . . . . . . . 152
Flag 3: Flag not used . . . . . . . . . . . . . . . . . . . 152
Flag 4: Flag not used . . . . . . . . . . . . . . . . . . . 152
Flag 5: Flag not used . . . . . . . . . . . . . . . . . . . 152
Flag 6: User gets SysOp status in this conference . . . . . 152
Flag 7: Deny the user access to this conference . . . . . . 152
Flag 8: Deny netmail access in this conference. . . . . . . 152
Override Prescan sec . . . . . . . . . . . . . . . . . . . . 152
User allowed in door . . . . . . . . . . . . . . . . . . . . 152
User allowed RoseNet . . . . . . . . . . . . . . . . . . . . 152
MODULES TO ADD INTO MESSAGE PACKETS: ADD-IN FILES . . . . . . 153
Magazine name. . . . . . . . . . . . . . . . . . . . . . . . 157
File name. . . . . . . . . . . . . . . . . . . . . . . . . . 157
Security . . . . . . . . . . . . . . . . . . . . . . . . . . 157
CONFERENCE OPTIMIZE. . . . . . . . . . . . . . . . . . . . . . 158
EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
NOTES ON SAVING RMAIL.DAT INFORMATION. . . . . . . . . . . . . 158
SPECIAL CONFIGURATIONS FOR INDIVIDUAL NODES. . . . . . . . . . 159
ROSEMAIL OPERATIONS. . . . . . . . . . . . . . . . . . . . . . 164
Sysop Local Hotkeys. . . . . . . . . . . . . . . . . . . . . 165
Pre-scan QWK packets for net sysops. . . . . . . . . . . . . 166
Prescan Method A: "ROMAIL /P" prescan . . . . . . . . . . 167
Prescan Command Line Options (ROMAIL /P method) . . . . 168
Prescan Method B: TPA prescan with batch file. . . . . . . 170
Lock a user out of RoseMail. . . . . . . . . . . . . . . . . 172
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page ix
Settings to use if your hub has RoseMail . . . . . . . . . . 173
Option 12: Download your replies. . . . . . . . . . . . . 174
Option 13: Use current date/time. . . . . . . . . . . . . 174
Option 20: Do not send NDX files. . . . . . . . . . . . . 175
COMMAND SUMMARY. . . . . . . . . . . . . . . . . . . . . . . . 175
Conventions in Text. . . . . . . . . . . . . . . . . . . . . 175
What to do with command lines. . . . . . . . . . . . . . . . 175
ROMAIL.EXE . . . . . . . . . . . . . . . . . . . . . . . . . 176
The ROSEMAIL (DOOR.BAT) file command line. . . . . . . . . 176
Pre-scan for QWK packets . . . . . . . . . . . . . . . . . 177
RM.EXE . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
RM.EXE <no parameters> . . . . . . . . . . . . . . . . . . 179
RM.EXE <HUB> /S. . . . . . . . . . . . . . . . . . . . . . 179
RM.EXE <HUB> /I. . . . . . . . . . . . . . . . . . . . . . 179
RM.EXE RDX:<low>-<high>. . . . . . . . . . . . . . . . . . 179
IN CASE OF DIFFICULTY. . . . . . . . . . . . . . . . . . . . . 179
ESCaping unwanted changes. . . . . . . . . . . . . . . . . . 179
Use Ctrl-U (Undo) to back out of small changes . . . . . . 179
ESC to back out of all changes . . . . . . . . . . . . . . 180
Finding RMAIL.DAT. . . . . . . . . . . . . . . . . . . . . . 180
UPGRADING your ROSEMAIL. . . . . . . . . . . . . . . . . . . . 181
To change from an unregistered to a registered version . . . 181
From one minor version to another (e.g. from 1.60 to 1.70) . 182
ENVOI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page x
List of Screens
RRS Sysop Module: RoseNet conferences. . . . . . . . . . . . . 24
Caller's (RoseReader) RoseNet conferences. . . . . . . . . . . 26
Screen 1. The DOORS file. . . . . . . . . . . . . . . . . . . 56
Screen 2. Description of RoseMail for Callers.. . . . . . . . 56
Screen 3. The RoseMail System Manager's main menu . . . . . . 66
Screen 4. RoseMail System Manager: File Paths. . . . . . . . 71
Screen 5. Compression Program.. . . . . . . . . . . . . . . . 85
Screen 6. Decompression program.. . . . . . . . . . . . . . . 86
Compression: different versions of the same program . . . . . 87
Screen 7. Transfer protocol information . . . . . . . . . . . 90
Screen 8. Transfer Protocols: DSZ Command Lines. . . . . . . 92
Screen 9. Transfer Protocols: Environment Variable.. . . . . 92
Selecting RoseMail's internal protocols. . . . . . . . . . . . 94
Screen 10. Transfer Rate and Packet Limit Information.. . . . 100
Screen 11. Local Board Information. . . . . . . . . . . . . . 104
Edit the Trashcan file . . . . . . . . . . . . . . . . . . . . 107
Edit the trashcan file . . . . . . . . . . . . . . . . . . . . 107
Screen 12. Duplicate checking information.. . . . . . . . . . 109
Screen 13. RoseMail Options.. . . . . . . . . . . . . . . . . 111
RoseNet Information configuration. . . . . . . . . . . . . . . 118
RoseNet File Information screen. . . . . . . . . . . . . . . . 118
RoseNet Options. . . . . . . . . . . . . . . . . . . . . . . . 120
Screen 18. Networks/NetMail Main Menu.. . . . . . . . . . . . 125
Screen 19. Available Networks.. . . . . . . . . . . . . . . . 128
Edit hub information . . . . . . . . . . . . . . . . . . . . . 132
Screen 20. Defining your own network. . . . . . . . . . . . . 133
Screen 23. NetMail conference definitions.. . . . . . . . . . 135
Screen 24. Net Sysop Access.. . . . . . . . . . . . . . . . . 137
Screen ##: Prompt for network in which to enter translations. 139
Screen 25. Set translation codes for network mail.. . . . . . 140
Screen 26. Network taglines.. . . . . . . . . . . . . . . . . 142
Screen 27. Pointer Resets.. . . . . . . . . . . . . . . . . . 143
Screen 28. Choose to set your pointers Before or After the
selected date and time of scan.. . . . . . . . . . . . . . . 143
Screen 29. USERS.INF Reset. . . . . . . . . . . . . . . . . . 144
Screen 16. Set conference data. . . . . . . . . . . . . . . . 146
Screen 17. Set conference flags by user account.. . . . . . . 151
Screen 14. Modules to add to message packets. . . . . . . . . 154
Screen 15. Magazines and Periodicals. . . . . . . . . . . . . 157
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page xi
LIst of Tables
Table 1. RoseMail System Manager: List of Editing Keys . . . 59
Table 2. The #-variable and its substitutions in File Paths.. 81
Table 3: Sysop Local Hotkeys. . . . . . . . . . . . . . . . . 165
Table 4: TPA method, Batch File To Pre-scan QWK Packets . . . 171
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page xii
QBETADOC.TXT Fri 5 Feb 1993, 10:21
Hi, RoseMail Friends,
This is a request for your assistance with the wide beta docs for
RoseMail, including the Sysop's Guide to RoseMail and the Caller's
Guide to RoseMail.
These guides are in beta. Originally written for RoseMail v.
1.70, they are being updated to version 2.00 - rapidly!
I would VERY MUCH appreciate your taking time to jot down a few
notes - anything that occurs to you while you are using any part
of the documentation. Please let me know:
What is missing that you want to have in there? What can be cut?
(When remarking on this, please consider others as well as
yourself.)
What is confusing?
What is "inaccurate"? :-)
You can even say if you LIKE part of it |-)
There will certainly be a beta conference of some kind. I would
very much appreciate your remarks; thank you very much!
PLANS FOR NOW: The updated parts of the documentation are still
sketchy; I will be adding to them and polishing them during the
wide beta testing of RoseMail.
I plan to expand the section on RoseMail Operations in the Sysop's
Guide.
Thank you for your help, friends; with your help, not only the
RoseMail programs, but ALSO the docs, will be top-quality.
--Carol Whitney Fri 5 Feb 1993, 10:24
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page xiii
PREFACE (wide beta)
-------------------
State of the Guides Report, Fri 5 Feb 1993, 19:09
-------------------------------------------------
This is the first edition of the Wide Beta RoseMail Guides. This
version includes a rough update of the Sysop's Guide to RoseMail
and the Caller's Guide to RoseMail from 1.70 to 2.00. Both the
Guides were written for RoseMail v. 1.70, but neither was
released. I have not yet taken the time to remove the references
to version 1.70, but all information included in both Guides is
intended to be current, therefore to refer to version 2.00 as well
as to version 1.7x. Therefore, if you find text that no longer
applies, please point it out. One example would be the
requirement to rebuild RDX files weekly. Version 2.00 no longer
requires that you rebuild the RDX files unless you are installing
an update or upgrade.
The updated material in this version of the Guides is roughly
sketched in. The Guided Tour at the beginning of the Sysop's
Guide is still in rewrite, but a version of it is included here.
Information on the RoseNet routed mail system for both Guides is
in first-draft form, and may be missing sections, or be a little
sketchy. Please point out areas where you feel more information
would be helpful.
All suggestions for improvement are welcome. Keep in mind that
these guides are not intended to reproduce the online help
available in the RoseMail Door and the RoseMail System Manager,
but rather, to supplement that information or expand on it where
needed. The Guides are already large, but there is still room for
additional material where it is needed. The intent is to make the
Guides extremely easy to read and use, so any suggestions for
improved clarity are welcome.
Please post your reports in the Rose or RoseMail conference.
Thank you very much! --Carol
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page xiv
ACKNOWLEDGMENTS: Sysop's Guide To RoseMail
-------------------------------------------
Thanks to the RoseMail team:
To the designer/engineer of RoseMail, Vic Kass, thanks for cooking
up a program that attracted the attention of this slightly cynical
messenger with its reliabllity, speed, and excellent design.
To Drew Miller, RoseMail programmer, special thanks for the many
late night replies to long, hazy, fuzzy, questions while his eyes
turned square in response to the modem lights.
To A. Nonny Mouse, thanks for jumping in with a sqweeeeeek!
message to light up the night in the dark hours of winter.
Thanks to Victorians - of the Victoria, B.C. area:
To Joe Macmurchie, Chief Sysop of Big Blue & Cousins BBS, for
tolerating the trials of this Baby Sysop with the greatest of good
humor, and even jumping in at crucial moments with information
that led Baby Sysop safely through the Marshes of Multi-Nodes and
NetMail.
To Joe Carr and Steve Holland, co-sysops of Big Blue & Cousins for
lifting Baby Sysop out of the Quicksand at crucial moments.
To Geoffrey Mason, who took many long hours putting an early draft
of the Caller's Guide through his mental shredder with the
assistance of his trusty computer and modem. To Bill Hadden for
reading and providing helpful comments on the Caller's Guide.
To the callers who assisted my explorations: most particularly,
to Warren McFadyen, who called repeatedly under trying
circumstances. and to Matthew Skala for similar assistance. Also,
to Geoff Mitchell, Don Malins, Murray Ryan, Dan Jaundrew, Brian
Grainger, Robby Robson, and the other callers who put up with
various oddities and sundry unexpected effects.
Very special thanks to Sysop Catherin Gregory and Co-Sysop Kjell
Ohlsson of Earthshine BBS for regular and sometimes surprising (to
them, and sometimes to me) assistance as beta testers of the
Sysop's Guide and of the resulting RoseMail arrangements.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page xv
Special thanks also to the staff at Clark Development Company for
excellent support, particularly to David Terry, Steve Catmull and
Michael Leavitt for fast and complete replies to my questions
about PCBoard, and for their infinite patience with me.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 1
Sysop's Guide To RoseMail
INTRODUCTION
------------
This is the first release of the RoseMail Reference Guide. It is
in three parts.
This part is the "Sysop's Guide to RoseMail."
The second part is the "Caller's Guide to RoseMail", which we hope
you will post for your callers. Also, we hope you will glance
through it yourself. If you call other RoseMail systems for mail,
you will want to keep it handy for reference, because it contains
information you may need which is not included in the Sysop's
Guide to RoseMail.
The third part is the "Guide to RoseMake". RoseMake is the
program you can use to create Magazine or Add-In files to post for
your callers.
Our purpose in these guides is to explain, as clearly as possible,
how to set up and use RoseMail, whether for brand-new sysops or
callers, experienced ones, or ones whose first language may not be
English.
We hope you will enjoy these guides.
If you have questions, comments, or suggestions concerning these
guides, RoseMail or RoseReader, please write to Vic Kass, Drew
Miller, or Carol Whitney. You can reach us in the RoseMail and
RoseReader conference on the RoseNet, U'NI-net, Smartnet or
Intelec networks, or on Salt Air BBS, in the Rose conference
(#48). We would like to hear from you.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 2
ROSEREADER FOR SYSOPS
---------------------
You may wish to try RoseReader for Sysops, which is available from
Rose Media BBS and other RoseMail systems, in a Test Drive
version. Response from those who have tried it is enthusiastic.
Your guide's writer uses it with delight.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 3
ABOUT THIS GUIDE
----------------
At the beginning of this guide, you will find a "Guided Tour" that
will show you where you are going when you install and configure
RoseMail. We particularly recommend that you read it if you are
installing RoseMail for the first time. You may wish to return to
it later if you lose track of the broad view while digging into
the details of installation and configuration. This tour includes
a short description of the main features of RoseNet registered,
routed direct mail system
Following the Guided Tour, we provide a section called
QUICK-INSTALL, so that if you are in a hurry and do not need to
consult the detailed reference portion, you can set up RoseMail
and get it running as quickly as possible. Once it is set up and
configured, the main reference section will provide additional
details.
The main reference section of this guide tells first how to
install RoseMail with PCBoard as a "Third Party Application", and
then describes the RoseMail System Manager (RM.EXE), which is the
program you use to configure RoseMail for your system. The main
reference section tells in detail how to configure RoseMail for
the first time, and also how to maintain RoseMail and make changes
to its configuration.
A brief section on RoseMail operations follows the main reference
section. After that, you will find a section on RoseMail
commands, a very short trouble-shooting section, and a note on
upgrading your RoseMail programs.
A guide to RoseMake, a program which allows you to "make"
Magazines and Add-In files, is included with this documentation
package in a separate file. This guide is entitled "RoseMake
User's Guide".
Wide beta note: The RoseMake Users Guide is in revision, not
ready yet.
If you are calling a RoseMail system yourself, you will need to
keep the Caller's Guide to RoseMail, also included in this
documentation package, at hand for reference. The Caller's Guide
to RoseMail contains information not available in the Sysop's
Guide.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 4
IMPORTANT NOTE on finding your way around the Main Reference
section of this guide:
We have tried to include all the essential information you need
to install, configure, and maintain RoseMail. As a result, in
the main reference section, much information is interspersed
between the paragraphs that describe the steps that you take
when you install and configure RoseMail. Therefore, the
"action" steps that you take during installation and
configuration have been assigned paragraph numbers and letters.
Because sometimes these paragraphs are spread far apart by the
informative paragraphs, you could look for these designations
if you want to find your way around the Main Reference section
as quickly as possible. Or you can use the Quick-Install
section as a kind of "index" to the Main Reference section,
since the step numbers there are the same for the same actions
as the step numbers in the Main Reference section.
SYSTEM REQUIREMENTS FOR RUNNING ROSEMAIL
----------------------------------------
To run RoseMail, you require:
256k of free memory at the time that DOOR.BAT runs. (See the
Guided Tour for more information.)
100% IBM-compatible DOS, version 3.1 or higher, on an 8088, 8086,
or 80286 machine or better.
PCBoard 14.5 or 14.5a by Clark Development Company. version /2 or
higher.
GUIDED TOUR
-----------
WIDE BETA notes on the Tour Guide
---------------------------------
I plan to cut and revise this section. Please help by pointing
out areas that can be omitted, or areas that you wish to see kept.
Thank you! I am thinking of organizing the information under
filenames.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 5
This is a guided tour to introduce you to the most prominent
filenames, directory structures, and elements of configuration you
will encounter when you install and configure RoseMail.
This section provides you with a broad view, and it includes some
detailed information you will need to understand if you are to
follow easily the instructions in the main reference section. We
refer you back to the Guided Tour where necessary, so you should
read through it for a quick understanding, and return to it if you
need to later. For full instructions on completing any step in
installing and configuring RoseMail, you should consult the main
reference section.
The following information should provide you with an understanding
of where you are going, so that you can proceed with confidence.
The PCBoard-RoseMail Link
-------------------------
You require PCBoard version 14.5 or higher in order to install
RoseMail. RoseMail provides you with a QWK-compatible mail door.
This door allows your callers to download QWK-format mail packets,
read them offline, log back on, re-enter the door, and upload
their replies. At the time the caller enters RoseMail, PCBoard
provides RoseMail with data concerning the current caller's
conference selection and message pointers, and then backs out of
the way, and allows RoseMail to load. When the caller leaves
RoseMail, RoseMail passes the caller's updated data back to
PCBoard. The QWK-format RoseMail Door is the first major feature
of RoseMail.
Netmail software in RoseMail
----------------------------
RoseMail's second major feature is its management of network, echo
mail in QWK format. Netmail exchange software is built into the
program as an integral unit.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 6
RoseNet registered, routed mail
-------------------------------
The third major feature of RoseMail, new with version 2.00, is the
RoseNet registered, routed mail system. Callers and sysop can
send routed private mail to any other RoseNet system. RoseNet
mail exchange can take place between all RoseNet systems, and can
also be gated to the Internet, thus to organizations such as
Compuserve and Prodigy. Rose Media BBS in Toronto is the central
host for all links.
Routing information is updated as systems are added, and the
routing map files arrive automatically at each system that is a
member of the RoseNet link. The map files arrive at your system
via RoseNet message as an attached .ZIP file, which you extract
with the W (Write) command, and unzip in the RoseMail \DM (map)
directory.
This third feature, RoseNet, has no direct link with PCBoard;
rather, it co-exists alongside PCBoard and your QWK-format door.
The RoseNet routed mail system requires that its users, including
you, the sysop, have a registered copy of RoseReader. Your copy
will be the RoseReader for Sysops version, and your callers who
are not sysops will use the regular RoseReader (Platinum version).
There is no direct link between RoseNet messages and your regular
PCBoard-format messages. If you wish to pass the contents of
RoseNet messages to PCBoard conferences, or vice versa, you will
need to save the existing message as an ASCII text file, and then
import it in the other format.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 7
Installing RoseMail with PCBoard
--------------------------------
When you install RoseMail with PCBoard, you begin by using the
PCBoard System Manager (PCBSM.EXE) to install a "Third Party
Application". When you do this, PCBSM.EXE adds some space to the
PCBoard USERS.INF file, making room for RoseMail to pass
information about a caller's selected conferences and messages
back and forth between itself and PCBoard. The PCBoard file
USERS.INF acts as a storage area for information needed by both
PCBoard and RoseMail. You should be aware that your USERS.INF
file may also contain information for other doors that you run on
your system. RoseMail also uses and updates conference selection
and message pointer information that is stored in the PCBoard
USERS file.
The RoseNet registered and routed mail system new with version
2.00 is not linked with PCBoard, but operates through RoseMail's
two program files, ROMAIL.EXE and RM.EXE. This portion of
RoseMail is mostly self-installing and self-maintaining. You
configure the RoseNet mail system using the RoseMail System
Manager (RM.EXE). The information files for this mail system are
contained in DM.ZIP, which is included inside the main RoseMail
ZIP files. DM.ZIP is updated automatically from the central
RoseNet system, Rose Media BBS.
Instructions for installing and maintaining the RoseNet mail
system are included alongside those for the PCBoard-linked
portions of RoseMail. Now we return to RoseMail's links with
PCBoard.
When a caller runs RoseMail, PCBoard and RoseMail cooperate to
make temporary work files such as USERS.SYS and DOOR.BAT.
DOOR.BAT runs the door program, and USERS.SYS passes any necessary
information from PCBoard to RoseMail. When the caller exits
RoseMail or logs off your board from the RoseMail Door, the
USERS.SYS file passes updated information about conferences and
message pointers from RoseMail back to PCBoard. Both the USERS
and the USERS.INF files are updated as needed.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 8
What is a node?
---------------
You can think of a node as the point (place) where a person makes
contact with your BBS system. A node is like a two-way pipeline,
or feeding station, where information is passed from the BBS to
the caller and from the caller to the BBS. Even if you are
running PCBoard with only one node, your caller contacts your
system on that node. In this guide, when we say "Node 1", we mean
Node 1 on a multi-node system, and also, we mean the single node
on a system that has only one point of contact open at a time.
Node directory
--------------
For both PCBoard and RoseMail, the files for different nodes are
held in separate directories, or, for a system where a node has
its own machine and its own local hard drive, on separate drives.
The purpose in this arrangement is to avoid mixing up the
information relating to one node or its caller with that for
another node and another caller. PCBoard and RoseMail access the
SAME node directories, so that your files specific to any one node
(un-shareable files) will all be on that node's directory or
drive, whether they are related to PCBoard or to RoseMail.
Sysops who run only one node sometimes keep files specific to Node
1 (and its callers) in the same directory as the PCBoard program
files. It is possible for PCBoard and RoseMail to use your \PCB
program directory for node-specific files if you are running only
one node. This means you do not need to make a separate node
directory if you put up only one node. Some sysops may be set up
without a separate node directory just because at the time of
installation, there was no apparent advantage to setting one up.
For logical reasons, we recommend that you separate the physical
locations of the two kinds of files: those that are shared
between nodes (used by all nodes), and those that are specific to
your single node, that is, to the caller who contacts you on the
node. To do this, you make a separate directory for the Node 1
files. Consult your PCBoard manual to determine which PCBoard
files belong in the node directory.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 9
Normally you would keep files that are shared between nodes in the
\PCB directory if they are PCBoard program or shared data files,
and in the \PCB\ROSE directory if they are RoseMail shared program
or data files. You would keep files that contain information
specific to the node or the caller, in a separate directory (the
"node directory") that you make for this purpose. Remember that
the node directory will hold files relating both to PCBoard and to
RoseMail. If you are running only one node, and you wish to make
a separate node directory, you might call it something like \PCB1
or \PCB\NODE1.
By logical extension, then, you can see that if you should add
more nodes to your system later, it is a simple matter to create
more node directories, or copy node-specific files to that node's
local hard drive. Often you can copy the files from your Node 1
directory odr drive to the directories or drives for Node 2, Node
3, and so forth, and then reconfigure those files so that they are
appropriate for the node concerned.
In this guide, we refer to the PCBoard program directory as
"\PCB", so if your PCBoard program directory has a different name,
you should keep that in mind as you read. Files specific to nodes
other than Node 1 (that is, those for nodes 2, 3, and so forth)
must be kept in their own, separate, node directories, which you
might name \PCB\NODE2 or \PCB2.
To summarize: node-specific files keep track of one node and its
current caller, and both PCBoard and RoseMail node-specific files
will be in the node directory. Program and shared data files
manage your BBS system for all nodes from their shared or common
location in the program directories, with PCBoard program and
shared data files being in the \PCB directory, and RoseMail
program and shared data files being in the RoseMail program
directory.
Besides having your PCBoard program directory, you will need a
RoseMail program directory to hold both the program files, and the
data files that are common to and shared by all nodes. Versions
of RoseMail from 1.70 and up are especially well designed to allow
you to share information between nodes as much as possible, so as
to simplify your configuration and lessen your maintenance of
individual nodes. You will see how this is managed as you
continue this tour.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 10
RoseMail makes the node directory the current directory
-------------------------------------------------------
Unlike some doors written for PCBoard, RoseMail by preference
leaves the caller logged onto the node directory. We recommend
that you follow this preferred structure, because it will simplify
all RoseMail operations. This structure is in contrast to PCBoard
door programs that log the caller onto the door program's
directory. The examples we provide in this guide all assume that
the DOOR.BAT file - the file that starts the door running for the
caller - leaves the caller logged on to the node directory for the
duration of all that caller's RoseMail operations.
The significance of this is that for all RoseMail operations,
assuming you follow the recommended structures during
installation, the node directory is also the current directory.
If you are aware of this, you may avoid the pitfalls that can
occur for a sysop who might mistakenly be thinking that the caller
is logged onto the RoseMail program directory.
RoseMail 2.00 comes with internal protocols. You will configure
these as desired during your installation. You may, however, use
external protocol programs. One point you need to keep in mind is
that any external program(s) that you install with RoseMail to
provide Transfer Protocols must be in the DOS search path.
Putting these programs into the current directory would be
wasteful on some systems, because the current directory during
RoseMail operations is the node directory, so that if you are
running more than one node, you would need separate copies for
each node. If you have a separate machine for each node, however,
you may wish to speed up local operations on some nodes by
providing copies of these programs on each node that has a local
hard drive.
You will be using external compression and decompression programs
of your choice, and these, also, must be in the DOS search path if
RoseMail is to find them.
What you want to remember, then, is that RoseMail treats the
caller's node directory as the current directory. All operations
while the caller is in the door are called from the node
directory. This is true whether you are running only a single-
node or multiple nodes, and it is true whether your Node 1
directory is the same as your PCBoard program directory, or
whether your Node 1 files are kept in their own, separate
directory.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 11
ROSEMAIL, the "KEYWORD" file
----------------------------
As mentioned earlier, the batch-like file that starts up the
RoseMail Door for your callers can be shared between all nodes on
your system. Therefore, this file, which we call ROSEMAIL in this
guide, belongs in the RoseMail program directory, where all nodes
can access it. When you place the ROSEMAIL file in the RoseMail
program directory, you avoid having to put a different ROSEMAIL
file in each node directory. At the same time, you avoid having
to edit many different ROSEMAIL files if you change your
configuration.
When you are installing RoseMail, using PCBSetup, editing the
DOORS.LST file under Main Board Configuration, PCBSetup asks you
for a "KEYWORD" to use as a PCBoard command that a caller can use
to open the door. In this guide, we suggest you use the KEYWORD
"ROSEMAIL", since it is easy for a caller to remember to type
"rosemail" to use the RoseMail Door. Of course, callers may also
use the traditional OPEN or DOOR commands to open the RoseMail
Door.
During your installation, shortly after you specify the KEYWORD to
open the door, you create the batch-like KEYWORD file (called
ROSEMAIL in this guide). As you create it, you will see how it
resembles a DOS batch file, in everything except its filename,
which has no extension. This file contains a command line for
ROMAIL.EXE, which is the program that runs the RoseMail Door for
your callers.
For example, if C is the drive you run from, your ROSEMAIL file
would normally be as simple as this:
C:\PCB\ROSE\ROMAIL
BOARD
You can see that the command line in the KEYWORD file ROSEMAIL
(the first line in the example above) resembles the command you
would type at a DOS prompt. It contains the drive\path\filename
of the program to be run (ROMAIL.EXE).
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 12
Normally, no further information is needed on this command line.
However, if you should choose to configure one or more nodes in a
special way, different from your global configuration, you can
create branches in the ROSEMAIL file to accommodate these. If you
create such branches, the command lines in the special branches
will probably require certain additions, such as an indication of
where to find the special RMAIL configuration file for the node in
question (see below for a description of this file). You will
find descriptions of how to manage these branches in the main
reference section of the guide.
You can make the branch by taking advantage of the DOS environment
variables that PCBoard 14.5a will provide automatically, or by
setting similar DOS environment variables in your BOARD.BAT or
AUTOEXEC.BAT for the node concerned (if you have not upgraded from
PCBoard 14.5 to 14.5a).
Branching is documented in the main reference section; however, we
will mention here that the command line for each branch you make
will start in the usual way, with the drive\path\ROMAIL part. For
a special configuration, you may then add one, or even two, more
specifications to the command line. The first addition would be a
drive\path\filename to a special RoseMail configuration file
("RMAIL.DAT" or "RMAIL.<node number>") that you have made for the
node concerned. The second specification you might add is what we
call an "/n switch". The "/n switch" merely specifies the number
of the node concerned, and it is only necessary if you have
configured your File Path to PCBOARD.SYS in the old way, common to
RoseMail 1.60 and earlier versions. The old way consisted of
using the "#-variable" in the file location for PCBOARD.SYS. This
old way is described briefly later in this guide.
What happens to the KEYWORD file ROSEMAIL
-----------------------------------------
When a caller types the command "rosemail" or "door <door number>"
or "open <door number>" from the PCBoard Command prompt, PCBoard
takes a copy of the entire KEYWORD file from the RoseMail program
directory, adds some information related to the DOS and PCBoard
environment for the node the caller is on, and drops this new file
neatly into the caller's current directory, which, for RoseMail
(configured as we recommend in this guide), is the node directory.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 13
PCBoard names this copy-with-additions DOOR.BAT. So, you can see,
DOOR.BAT incorporates the (keyword) ROSEMAIL file, but is not the
same as the ROSEMAIL file, because the KEYWORD file, ROSEMAIL, is
a global file that pertains to all nodes on your system, but
DOOR.BAT contains some information specific to the current caller
and to the node where the caller is logged on. Furthermore,
DOOR.BAT gets placed in a directory different from where the file
ROSEMAIL is, and DOOR.BAT "directs operations" from the node
directory, instead of from the RoseMail program directory.
So, you can think of the ROSEMAIL (KEYWORD) file as being global,
while the DOOR.BAT file made from it is specific to the node and
to the caller who occupies the node.
You might also notice that the ROSEMAIL file, that is, the KEYWORD
file, does not itself actually run anything. The DOOR.BAT file is
what does the running. When the caller exits RoseMail, PCBoard
erases the DOOR.BAT file from the node directory, to clear the
node for the next caller. After DOOR.BAT is erased, PCBoard
checks the USERS.SYS file, passes any updated information back to
the USERS and USERS.INF files as necessary, and then erases the
no-longer-needed USERS.SYS file.
You may, of course, use any legal DOS <filename> for the KEYWORD
file. In this guide we call it ROSEMAIL (no extension), with the
idea that callers can easily remember "rosemail" as a command to
type in PCBoard.
Tour of RoseMail operations
---------------------------
A caller logs onto your system. This caller is logged onto the
node directory, which is also the current directory. Now the
caller types "rosemail" or "door <number>" or "open <number>".
PCBoard now creates the USERS.SYS file in the caller's current
directory (the node directory), and then goes to your RoseMail
program directory, copies the contents of the global KEYWORD file
ROSEMAIL, adds any necessary information specific to the node and
the caller, names the new file DOOR.BAT, and places this DOOR.BAT
file in the caller's current directory (the node directory).
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 14
The ROSEMAIL file contains a command line that starts ROMAIL.EXE,
which is the program that runs the RoseMail Door for your callers.
Therefore, DOOR.BAT also contains this command line. Because
DOOR.BAT is in the node directory, but ROMAIL.EXE is in the
RoseMail program directory, the command line in ROSEMAIL (and
DOOR.BAT) contains a full drive and pathname to ROMAIL.EXE.
ROMAIL.EXE needs to be able to find three of PCBoard's node-
specific files: PCBOARD.DAT, PCBOARD.SYS, and USERS.SYS. Each
node directory has its own copy of these files.
PCBOARD.DAT is the configuration file you created with PCBSetup
when you set up the node for PCBoard. PCBOARD.SYS is a node-
specific file which is managed by PCBoard. It keeps running track
of caller and node information. USERS.SYS is a node-specific file
which is created when the caller starts RoseMail operations, and
it is the file that keeps track of that caller's operations on
your system. When you configure RoseMail, using the RoseMail
System Manager (RM.EXE), you specify where these files are to be
found, using the File Paths menu.
Because in normal RoseMail installations, the caller remains
logged onto the node directory, and that directory is therefore
current, your RoseMail configuration will work best if you specify
the current (node) directory for the location of these files.
This means you can usually omit any drive and pathname while
configuring the File Paths using the RoseMail System Manager, and
use only the <filename.ext> to specify the locations of
PCBOARD.DAT, PCBOARD.SYS, and USERS.SYS. When you configure this
way, ROMAIL.EXE will look in the current directory for these three
files, thus finding the correct files for the current caller.
When the caller exits RoseMail, either by logging off from the
door or by returning to PCBoard, PCBoard deletes that node's
DOOR.BAT from the node directory, and then uses that node's
USERS.SYS file to update conference and message information for
that caller. The updated information is stored in the USERS.INF
and USERS files.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 15
RoseMail's configuration file: RMAIL.DAT
-----------------------------------------
After you have installed RoseMail in PCBoard using PCBSM.EXE to
"add a Third Party Application", you configure RoseMail to fit
your system. You do this by logging onto the RoseMail program
directory and running the RoseMail System Manager (RM.EXE).
When you exit RM.EXE and save your configuration, RM.EXE creates
RMAIL.DAT in the current directory. While you are configuring
RoseMail, you will NORMALLY be logged onto the RoseMail program
directory. The purpose of this is to save the RoseMail
configuration file, RMAIL.DAT, in the directory where all nodes
can share the same information. That is, all nodes access
RMAIL.DAT, which is stored in your RoseMail program directory.
Since you were logged onto the RoseMail program directory, called
C:\PCB\ROSE in this guide, this RMAIL.DAT, which affects all nodes
on your system, is saved in C:\PCB\ROSE (or its equivalent, if you
should happen to have a different name for your PCBoard program
directory).
RoseMail 2.00 provides a second configuration file which is, by
default, called CONFDATA.DAT, although you can call it anything
you wish. CONFDATA.DAT stores conference flags, which determine
access to conferences, and network conference translation tables,
which match your conferences to the conferences on your hub. Like
RMAIL.DAT, CONFDATA.DAT is a shared file, so it is normal to store
it in your RoseMail program directory, or "RMail directory", as we
call it in this guide. This directory would be C:\PCB\ROSE (or
its equivalent on your system).
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 16
Special RoseMail configurations for individual nodes
----------------------------------------------------
RoseMail allows to you make special configurations for individual
nodes. You might, for instance, want to run one node on a
RAMdisk, or make some other special arrangement for that node. If
you choose to do this, you can create a separate, node-specific
RoseMail configuration file for that node, by logging onto the
node directory (so that it is current), and using the full drive
and pathname to start the RoseMail System Manager. When you save
this node-specific configuration file for the first time, it will
be called RMAIL.DAT. You can rename the file under DOS. The
advantage of renaming this special RMAIL.DAT is that you can see
at a glance that it is meant for one node only. You might, for
instance, call it RMAIL.<node number>.
If you choose not to rename RMAIL.DAT, you will need to take extra
care, when configuring this special node, to log onto the node
directory (or drive) BEFORE you start up the RoseMail System
Manager (RM.EXE). If you start RM from the RoseMail Program
directory, it is going to use the RMAIL.DAT from the default
location (that is, C:\PCB\ROSE), and you will be putting
information that belongs to the special node into your globally
accessed RMAIL.DAT. This kind of error could cause havoc on your
system.
Therefore, we recommend that for all special RMAIL.DAT files, that
is, those that apply only to one node, you rename the files so
that you can identify them as belonging to a specific node.
Another protective measure you might use is to write batch files
to access these special RMAIL.DAT files, because otherwise, you
can still be subject to the error of forgetting to log onto the
special node's node directory before starting RM, and once again,
you could find yourself configuring the global RMAIL.DAT file
instead of the one you intended to configure.
To make sure you access the correct configuration file (RMAIL.3,
or whatever it is called for that node) if you are working on the
specially-configured node, log onto the node directory concerned
first, and then issue the following commands
c:\pcb\rose\rm rmail.<node number>
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 17
You do not have to rename this RMAIL.DAT file if you do not want
to, because RM.EXE and ROMAIL.EXE will look first in the current
directory for its RMAIL.DAT file, and if it does not find one in
the current directory, it will look in your \PCB\ROSE directory
(common or shared program directory) for the RMAIL.DAT file.
Renaming a specialized RMAIL.DAT file would, then, be for your own
convenience in seeing that the file is one that belongs to a
specific node.
For example, when making a special configuration file, you could
use either of the two following patterns, on the DOS command line,
or, if you prefer, in a batch file:
cd\pcb\node3
c:\pcb\rose\rm
OR, if you have renamed your RMAIL.DAT for Node 3 to RMAIL.3:
c:\pcb\rose\rm c:\pcb\node3\rmail.3
What you need to remember, then, is that all your nodes that share
a common configuration will use the global RMAIL.DAT file. This
RMAIL.DAT file remains in the RoseMail program directory, where it
is accessible to all nodes on your network. But a node for which
you make a special configuration has its own version of the
RMAIL.DAT file, which is stored in the node directory (or on the
node drive) concerned, and is available only to that node.
If your RoseMail is registered, each of these configuration
(RMAIL.*) files requires a ROSEMAIL.KEY file in the same directory
in which it is located. So you will always need a copy of your
ROSEMAIL.KEY in your \PCB\ROSE directory, and if you have a
special configuration file for, say, Node 3 (RMAIL.3, for
instance), you will copy your ROSEMAIL.KEY to C:\PCB\NODE3 (or its
equivalent).
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 18
The RoseMail Work Directory
---------------------------
During caller operations, RoseMail creates a temporary work
directory to manage mail packets for the current caller (which is
the same as saying "the current node"). As you can imagine, each
caller (or node) needs a unique work directory, since the mail
packets are specific to the caller and the node, and the callers
would probably prefer having their own mail packets to receiving
some jumble of packets half of which belonged to another caller.
You can surely imagine, too, that RoseMail cleans up after itself,
so as not to leave one caller's information mixed up with that of
the next caller on the node, or with that of another caller on
another node.
When you configure RoseMail, you are asked for the drive, path,
and directory name for the Work Directory. Therefore, what you
want to do here is to specify a name containing some kind of
variable, so that each node's work directory can be kept separate
from that of any other, even though you are using only a single
configuration file to specify the Work Directory. Fortunately,
RoseMail makes this easy to do.
When you first install RoseMail, your default Work Directory
specification comes as:
C:\PCB\WORK#
The "#" in that line is what we call the "#-variable". RoseMail
will substitute for "#" the number of the node that the caller is
on at the time RoseMail is accessed. You can see that in this
way, each node's work directory will be different from any other,
because it will have a unique name. This is important because
RoseMail erases all the files in the Work Directory, and then
erases the directory itself.
The implication is clear: you should make sure that the name of
the Work Directory is not the same as that of any directory that
already exists and contains files you need to keep. The default
configuration that comes with RoseMail should work for most,
perhaps all, systems.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 19
The only items you would probably need to change from the default
shown above for the Work Directory would be the drive letter, or
if your PCBoard program directory is not called \PCB, naturally
you would need to change that name also.
If you like to type extra letters, you could use "%PCBNODE%"
instead of the "#" illustrated, providing that you have a DOS
environment variable PCBNODE set (either by PCBoard 14.5a, or in
your BOARD.BAT for each node, if you are running PCBoard 14.5).
ROSENET MAIL
------------
Introduction to RoseNet
-----------------------
The RoseNet registered, routed mail system is new with RoseMail
2.00. Read the WHATSNEW.200 file that comes with the package for
a list of the features it includes. Here, we cover briefly the
features that you, the sysop, need to configure and maintain, and
present the common operations you will be using as a RoseNet
sysop. We mention caller operations in passing, where the sysop
needs to be aware of them. The Caller's Guide to RoseMail covers
caller use of RoseMail, but not the offline use of RoseReader.
See the RoseReader documentation for further details.
Because the RoseNet system is largely self-installing and self-
maintaining, because it includes detailed online help, and because
in many of its procedures, its operations resemble other RoseMail
operations, we concentrate here on the information that goes
beyond that offered in the online help or in the other parts of
this documentation.
Installation and configuration of the RoseNet mail system is
covered in the Quick-Install section, and again in the main
reference section of this guide.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 20
RoseNet mail exists separately from PCBoard. You need either a
registered copy of RoseReader for Sysops Lite, which comes free
with RoseMail, or a registered (Platinum) copy of RoseReader for
Sysops, which allows you to open QWK packets as well as to use the
Sysop Module, in order to access the Sysop functions of RoseNet
mail. Your callers who have registered (Platinum) copies of
RoseReader, or copies that function fully on your own BBS only,
can use the RoseNet mail system from their QWK packet menus.
By arrangement with Rose Media, you can provide callers with
copies of RoseReader that are fully functional on your own board
only. To be eligible for this arrangement, you make a commitment
to install and maintain a daily RoseNet link with your RoseNet hub
system. If you are interested in providing such an arrangment for
your callers, you may log onto Rose Media BBS at (416) 733-2285,
join Conference 1 (MSG2SYSP), and leave a Comment to the sysop.
Callers whose RoseReader packages are specific to their local
boards enjoy the full range of RoseReader functions - but only on
their home boards. See the RoseReader documentation for further
information on these topics.
RoseNet Features
----------------
Range for RoseNet messages
--------------------------
Using RoseNet, your callers and you can send messages apart from
the networks you carry. You can send messages into the Internet,
and you can reach services such as CompuServe and Prodigy this
way. You can send UseNet messages using this system. Your
messages are automatically private, and they are routed through
Rose Media BBS, the central host for this system.
Sysops of RoseNet systems receive a free registered copy of
RoseReader Lite for Sysops. This program has all the features of
RoseReader for Sysops, except for the ability to read QWK packets.
Your RoseReader Serial Number is an integral part of the entire
RoseNet system. This number acts as your personal RoseNet
identity and address. You can be reached via the RoseNet BBS
system as "SYSOP@<your packet name>." On the Internet, your
address is:
rn.<4-digit serial number>@rose.com
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 21
For instance, you can reach RoseMail and RoseNet developer Vic
Kass through the Internet at the address "rn.1001@rose.com". You
can be reached on the Internet at the address "rn.xxxx@rose.com",
where "xxxx" is your RoseReader serial number. However, you as
part of the RoseNet BBS system, would normally reach Vic Kass, or
anyone else linked to the RoseNet system, through the BBS gateway,
rather than through the Internet Gateway, so as to use the faster
means of contact, and avoid overloading the Internet gateway
system.
REMINDER: When you can reach another sysop or caller via the
RoseNet BBS link, you should use the BBS gateway, first, because
the link is more efficient than an Internet gateway link if your
recipient is part of the RoseNet system, and second, to avoid
unnecessary loads on the RoseNet Central Host's Internet gateway.
Your consideration in this matter is important! We thank you in
advance for it.
RoseNet Message features
------------------------
RoseNet messages are compressed, so they take up less room on your
system than PCBoard messages. They are decompressed at the time
of access, and recompressed when you leave the message. The
messages can be re-edited, in the Sysop Module, with the (M)odify
command, and by callers from their QWK packets, by using the
(R)eply command from the RoseNet Replies conference.
All RoseNet messages contain an audit trail. This trail can be
seen from any message while browsing it, by pressing H. If the
message is saved as a text file, the audit trail is included in
the text file. The audit trail shows where slow points are in the
link, and otherwise facilitates the tracking of RoseNet messages.
You may request return receipts for your messages (request return
receipt), check that the user you are addressing is known on the
destination system (User Check), scramble (encrypt) your message
(scramble code), and attach a file to your message.
Return receipts and User Checks are requested from the message
information window that the caller fills out at the time the
message is written.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 22
The writer of a scrambled RoseNet message must deliver the correct
scramble code to the recipient. Scramble codes are case-
sensitive.
The local sysop, and the sysops of systems enroute to and from the
RoseNet Central Host, may configure limits to the size of attached
files. Files are attached when the message information window is
filled out, by entering the drive, path, and filename of the file
to be attached. The recipient of the file detaches it at the
other end by using the (W)rite command while viewing the message.
You can enter a RoseNet message from anywhere on your board, using
RoseReader for Sysops or RoseReader for Sysops Lite. Similarly,
callers who use RoseReader can enter a RoseNet message from
anywhere in their QWK packets. To enter a RoseNet message while
browsing a PCBoard conference, simply press the space bar to
toggle the first field in the Message Information Window, which
defines the type of message, from PCBoard to RoseNet.
You and your callers can encrypt messages by entering a scramble
code in the Message Information Window. Passage and delivery of
encrypted messages depend on the configuration chosen by the sysop
or sysops along the route that the message travels.
The sysop of each RoseNet system controls the passage of encrypted
messages. Where a message arrives on a system where the sysop has
configured to refuse encrypted messages, an encrypted message will
be bounced back to its writer, explaining the problem.
Other RoseNet messages may be bounced back to the writer for other
reasons, such as, when a User Check has been requested by the
writer, and the user is unknown on the destination system, or when
the message is not deliverable for some other reason.
Registration of software via RoseNet
------------------------------------
You and your callers can register copies of RoseReader, RoseReader
for Sysops, and RoseMail, by using the REG command in your
RoseMail Door and downloading the KEY file that comes back to you.
You are notified of the arrival of your KEY file when you enter
the RoseMail Door, and you are prompted to download it.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 23
To register RoseMail or RoseReader, a caller (who may also be a
RoseMail or RoseNet sysop) logs onto your BBS and opens your
RoseMail Door. Once there, the caller types "REG" at the RoseMail
Command prompt. Thereafter, the caller is prompted for the
necessary information. Registration can be accomplished by credit
card, or by cheque or money order. When the registration
information is complete, the caller receives notice that the
registration message is being sent, and is then returned to the
RoseMail Command prompt.
The saved message that contains the registration information is
added to the RoseNet packet that goes up to the next system.
Because this information is sensitive, it is not included in any
of the sysop-readable conferences; instead, it is inserted
directly into the RoseNet packet. It is included with your
HUB.REP packet at the time you scan for outgoing mail.
Other companies and authors may make arrangements to take
advantage of this system of software registration by contacting
Vic Kass, Rose Media Inc., P.O. Box 345, Station 'A', Willowdale,
Ontario, M2N 5S9, Canada.
NOTE: Sysops of RoseNet systems should generally plan to upload
the HUB.REP file before downloading the HUB.QWK file. For any
registration previously authorized, the delivery of KEY files will
be immediate. The request for the KEY made in the upload triggers
the registration, and the registration KEY file is then sent in
the HUB.QWK during the same call.
Once you have installed and configured the RoseNet registered,
routed mail system, you can look at its structure by starting
RoseReader for Sysops. We present enough here to show you what
the installed RoseNet system looks like. For further information,
please consult the documentation for RoseReader and RoseReader for
Sysops.
To access the Sysop portion of RoseNet, you press S from the QWK
packet menu of RoseReader for Sysops. You can see, among the
conferences at the top of your conference list, four pseudo-
conferences that are new with version 2.00 of RoseMail and
RoseReader.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 24
When you press S from the RoseReader for Sysops QWK packet menu,
you will see a screen that looks something like the following
illustration. Naturally, your PCBoard conference names will be
different. The pseudo, "Non-BBS" conference names, however, will
have the same names on every system. The screen that follows is
cut down, to omit a long list of irrelevant conferences; it shows
the RoseNet conferences that you, the sysop, have access to.
Asterisks in the left margin of this illustration designate the
RoseNet conferences. You do not see any such marker on your own
system; these asterisks are merely to point out the location of
these conferences.
Screen ##: RRS Sysop Module: RoseNet conferences
╔═════════════ Select a Conference (SYSOP) ═══════════╗
║ Archive SavRoseNet ║
║ Personal Beginners-PN ║
* ║ Sysop RoseNet PACAdmin-PN ║
* ║ RoseNet Archives Reserved ║
* ║ RoseNet In Transit PC-Mania_PN ║
* ║ RoseNet Sent Reserved ║
* ║ Monitored Messages Reserved ║
║ Main Board CompuChat-PN ║
║ PCB-Rose_EN Documents ║
╚════ Conference Number : Non BBS ═══════════ More ══╝
The five Sysop Module pseudo-conferences are:
Sysop RoseNet - from where you read new RoseNet messages
you have received, reply, and write new
messages. This conference is packed
according to your configuration settings
in the RoseMail System Manager. Remember
that you can also enter RoseNet messages
while browsing PCBoard conferences, by
toggling the message type field in the
Message Information Window.
RoseNet Archives - which receives and holds messages that you
(D)epost in Archive (see the RoseReader
documentation for a description of this
feature). You can reply to RoseNet
messages from this conference. To pack
this conference, you kill messages as you
wish.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 25
RoseNet in Transit - which stores messages you have written
that are still active, in that they have
not yet reached their target. The target
may be a user or a net sysop on your
system, who would download the message.
The message will be deleted upon download.
Messages destined for a system you call
will be packed out (deleted) from the
RoseNet in Transit conference at the time
they are scanned into your HUB.REP. You
can (M)odify messages from this
conference. Messages are deleted from
this conference at the time they are
scanned to go out from your system.
Messages that fail to reach a user whose
membership expires, or who does not call
and download them, will not be packed out
automatically. The RoseNet packing
routines operate without your attention,
or you can start them up manually from the
RoseMail System Manager.
RoseNet Sent - which stores messages that have been
received by a user or net sysop on your
system, or those you have already scanned
to go into a HUB.REP. Incoming mail also
appears in this conference. This
conference is packed automatically, by the
regular RoseNet packing routines, with the
limitation that if a user fails to
download messages, or the user's
membership expires, messages for that user
will remain.
Monitored Messages - which stores RoseNet messages from your
callers if you have selected their names
for monitoring in the RoseMail System
Manager. To pack this conference, you
(K)ill the message by hand, or you can use
the Monitored Message pack routine from
the RoseMail System Manager. If you wish
to control fully what is kept and what is
packed out, you should pack this
conference manually.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 26
Your callers receive and send RoseNet messages in their QWK and
REP files. They require a registered version of RoseReader in
order to use this feature. RoseNet is available to callers only
through the RoseMail Door. Access is enabled to all callers who
have a security level equal to or greater than that designated by
the sysop for use of RoseNet. Should it become necessary, you can
shut callers out of RoseNet mail by setting a flag in the Users
Flags menu of the RoseMail System Manager (RM.EXE).
Your callers who access RoseNet will use RoseReader version 2.00
to do so. They will see the three pseudo-conferences on their QWK
packet menus, as illustrated below. Also, just as a sysop can
toggle the message type from PCBoard to RoseMail Point-to-Point
while browsing a PCBoard conference, callers can do the same from
their QWK packets, thus converting what was written as a PCBoard
message to the RoseNet format. A message toggled to Point-to-
Point format from PCBoard format is saved in the RoseNet Replies
conference. In the illustration below, we have marked the three
RoseNet conferences that show on the caller's QWK packet menu with
asterisks in the left margin of the illustration. RoseReader does
not mark these conferences; the marks here are simply to aid your
eye.
Screen ##: Caller's (RoseReader) RoseNet conferences
╔═════════════════ Select a Conference ══════════════════╗
║ Archive (49) S_SciFi ║
* ║ RoseNet Archives (1) S_ChitChat (19) ║
║ Replies (6) S_Asia ║
* ║ RoseNet Replies S_Travel ║
║ Personal (6) S_Writers ║
* ║ RoseNet S_Internation ║
║ Main Board S_Desqview ║
║ S_Astronomy I_Spitfire ║
╚════ Conference Number : Non BBS ═════════════ More ══╝
Your callers can enter and reply to RoseNet messages in their
RoseNet conferences, (D)eposit RoseNet messages for review and
later reply from their RoseNet Archives conferences, and review
and edit their RoseNet Replies in their RoseNet Replies
conferences. See the documentation for RoseReader for further
information. They can toggle a message between the two types,
PCBoard and RoseNet Point-to-Point, at will, when filling out the
Message information window.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 27
NOTE: A registered copy of RoseReader, that is, either a fully
registered Platinum version which accesses any PCBoard BBS, or a
version registered for use on the caller's home PCBoard BBS only,
is necessary for a caller to use the RoseNet mail system. Callers
who use other offline readers, however, may access your PCBoard
conferences through your RoseMail Door.
RoseNet Configuration
---------------------
Installation of RoseNet is covered in Quick-Install and in the
main reference section.
This concludes our orientation tour of RoseMail. You may now use
the Quick-Install section, which follows immediately, or you may
skip to the Main Reference section, which follows the Quick-
Install section. Are you ready? Go!
QUICK-INSTALL
-------------
In case you are in a hurry to get RoseMail up and running, here is
a quick guide to installing RoseMail. If you run into
difficulties, please consult the main reference section, which
begins with the heading "ROSEMAIL MAIN REFERENCE."
How to Use Quick-Install
------------------------
If you are installing RoseMail for the first time, we recommend
using the directory names illustrated (or a close approximation).
You may, however, need to substitute your own drive letters for
those shown here. Make sure to use the directory name \TEXT off
your RoseMail program directory (\PCB\ROSE or some similar name),
since that directory name is required for ROMAIL.EXE to find its
help and menu files This means that if your program directory is
\PCB\ROSE, your directory name for the help and menu (TXT) files
will be \PCB\ROSE\TEXT.
If you are upgrading from a previous version of RoseMail, you may
use your already-installed directory structure; refer to the Main
Reference section for assistance if you need it.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 28
For your convenience, step numbers here in the Quick-Install
section are the same as those in the main reference section. Some
of the steps in the main reference section are not included in the
Quick-Install instructions, so you may notice that some numbers
are skipped in this section. If you get stuck, check the step
number you are working with, and use it to refer to the main
reference section.
Before installing, read the file SETUP.200 that comes with the
RoseMail files. It is a short file, and will take you only a few
minutes to read. You may also read the WHATSNEW.200 file for
useful information.
Steps to perform for a quick installation
-----------------------------------------
1) BACKUP: Back up your system!
2) SYSTEM CONFIGURATION: Check your CONFIG.SYS file.
2-A) Make sure you have at least FILES=25 in your CONFIG.SYS
2-B) If you change your CONFIG.SYS, remember to save the new
file, and to reboot your system to allow the change to
take effect.
3) SUBDIRECTORIES: Make subdirectories to hold RoseMail files.
IMPORTANT! If you are running a multi-node system under a
network, RoseMail must be installed on a network drive.
3-A) Log onto your network drive, or if you are running only
a single machine or a single node, onto the drive where
you keep your PCBoard program files. You will be
creating subdirectories for files that are common to all
nodes on your system.
3-B) Make a subdirectory off your \PCB directory to hold the
RoseMail .EXE files.
Usually: MD \PCB\ROSE
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 29
d t) Make a subdirectory off the one you just made, and call
it \TEXT. Note: this subdirectory must be named
"\TEXT", and it MUST be off your \PCB\ROSE (RoseMail
program) directory, so that RoseMail can find its Help
text files.
Usually: MD \PCB\ROSE\TEXT
3-D) If you are planning to carry Magazine files, make a
subdirectory to hold them.
Usually: MD \PCB\ROSE\MAG
3-E) If you plan to carry Add-In files, you may make a
separate subdirectory in which to keep them.
For instance: MD \PCB\ROSE\ADDIN
3-F) If you will use Direct Mail, the RoseNet routed,
registered mail system, make a subdirectory to hold the
routing information and MAP files.
Usually: C:\PCB\ROSE\DM
4) EXTERNAL PROTOCOLS: If you plan to use external protocols
such as DSZ, make sure RoseMail will be able to find the
appropriate programs. We use DSZ as the main example here.
Make sure that either a DOS path is set to DSZ, or DSZ's
location is pointed to by the command lines contained in the
Transfer Protocols configuration screen (instructions for
doing this are given in the Main Reference section, under
"Transfer Protocols"). If you are multi-tasking, for
instance, with DESQview, you are probably running more than
one COM port on the same machine. You will speed access to
DSZ if you use the full drive and pathname on the command
line in the Transfer Protocols screen (RoseMail System
Manager). Otherwise, making sure DSZ is located in your DOS
search path will be sufficient for RoseMail operations. See
Step 4 in the Main Reference section for details.
5) Choose DOOR NUMBER and SECURITY LEVEL
5-A) Decide in what door (number) you will install RoseMail.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 30
5-B) Decide on the minimum security level you will require
for callers to use RoseMail.
6) COPY FILES
6-A) Collect your RoseMail files. Your filenames may begin
with "!"; however, we are omitting the "!" here to make
the filenames easier to read.
RM170A.ZIP
EXE files for 80286 machines and up (with some
information in text files as well)
RM170B.ZIP
EXE files for 8088 or 8086 machines (with some
information in text files as well)
RM170C.ZIP
RoseMail's menu and help files (*.TXT)
RM170D.ZIP
Text and information files, including this guide, the
Caller's Guide To RoseMail, and the RoseMake User's
Guide.
RM170E.ZIP
Sample Magazine files
ROSEMAIL.KEY
Registered versions only (download from the Rose Media
BBS REGISTER door at (416) 733-2285).
6-B) Unzip RM170A.ZIP (but if you are installing on an 8088
or an 8086 machine, use RM170B.ZIP instead). Now copy
RM.EXE and ROMAIL.EXE to your RoseMail directory.
Usually, copy these files to: C:\PCB\ROSE
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 31
6-C) If you have registered RoseMail, you have a file called
ROSEMAIL.KEY. Copy it to this same subdirectory
(C:\PCB\ROSE or its equivalent) now.
6-D) Unzip RM170C.ZIP, and copy all the .TXT files to
C:\PCB\ROSE\TEXT (or to the \TEXT subdirectory you made
in step 3-C above).
Usually, copy the files to: C:\PCB\ROSE\TEXT
6-E) If you are going to carry the Magazine sample files,
unzip RM170E.ZIP, and copy the files to your Magazine
subdirectory.
Usually, copy the files to: C:\PCB\ROSE\MAG
6-F) If you are going to use the Direct Mail, RoseNet,
system, unzip DM.ZIP and copy the files into your Direct
Mail directory.
Usually, copy the files to: C:\PCB\ROSE\DM
7) PCBSM: PCBoard System Manager.
7-A) INSTALL ROSEMAIL as a Third Party Application in PCBoard
7-A-1) !!! WARNING !!! TAKE ALL NODES DOWN!
Double-check that PCBoard is not running any node
on your system.
7-A-2) Start the PCBoard System Manager.
7-A-3) Select D, User Info File Maintenance, from the main
menu.
7-A-4) From the User Info File Maintenance menu, select C,
Add/Update Third Party Application.
7-A-5) When you are asked to enter the name of the Third
Party Application, enter "ROSEMAIL" (do not type the
quote marks).
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 32
7-A-6) When you are asked for Version, Static Size, Dynamic
Size,and Keyword, enter the following information:
Version: 1
Static Size: 256
Dynamic Size: 1
Keyword: ROSEMAIL
NOTE: for the "Version" number, do NOT put in the
minor version number (such as "1.70" - it is the MAJOR
version number ("1") that is required here.
7-A-7) Now press PgDn to let PCBoard modify the USERS.INF
file.
The information you have just entered will now be
written to disk.
7-A-8) You may find that another screen pops up asking you to
enter another Third Party Application name. If this
happens, press ESC to exit.
7-A-9) Press ESC to return to PCBSM's main menu. Now select
C, PCBSetup.
7-A-10) Select J, Main Board Configuration.
7-A-11) Highlight the DOORS.LST file, toward the lower
right side of the screen.
7-A-12) Press F2 to edit DOORS.LST.
7-A-13) Edit DOORS.LST, as follows:
7-A-13-a) Door Number: Press Alt-I to create a new
line. This will make a new door number for
you. Place your cursor beside the door number
you have chosen for RoseMail.
7-A-13-b) For the Filename, enter ROSEMAIL.
e, and t) Password: If you are going to require a
password for callers to open the RoseMail
Door, enter it in this field. If you do not
require a password, leave this field blank.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 33
7-A-13-d) For the Security Level ("Sec"), enter the
minimum security level your callers will
require in order to use your RoseMail Door.
7-A-13-e) Specify "N" under Login, unless you want your
callers to be forced into RoseMail immediately
following logon.
7-A-13-f) In the "USER.SYS" column, enter Y.
7-A-13-g) In the "DOOR.SYS" column, enter N.
7-A-13-h) In the "Shell" column (if there is one), enter
N.
NOTE: Version 14.5 of PCBoard will not show the
"Shell" column, since the Shell Door is new with
PCBoard version 14.5a.
7-A-13-i) In the "Path to DOOR Files" column, enter
C:\PCB\ROSE (change the drive letter if yours
is different).
Now, from this menu, you may edit (create)
your DOOR ("keyword") file, that is, the file
called ROSEMAIL. Notice that this filename
has no extension.
7-A-14) Highlight the filename "ROSEMAIL", and press F2
once more, to "edit the DOOR file".
Your text editor now loads, to let you create the
file C:\PCB\ROSEMAIL. When typed, the file should
look like this (change the drive and subdirectories
specified, if necessary):
C:\PCB\ROSE\ROMAIL
BOARD
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 34
7-A-15) When you have finished typing your ROSEMAIL file,
save it, and exit your text editor. When you do
this, you are returned to the "Edit DOORS file"
menu of the PCBoard Setup Utility.
7-A-16) Press ESC to return to the Main Board Configuration
menu of the PCBoard Setup Utility. You will be
asked if you wish to save the new configuration.
7-A-17) Save the new configuration.
7-A-18) The DOORS file listing is in the lower left area of
the Main Board Configuration screen, under "Menu
Listing." Press your Up Arrow to highlight the
DOORS file, and press F2 to edit it.
7-A-19) Type the information your callers will need,
showing the Door Number, the Name (RoseMail), and a
brief description of RoseMail for your callers.
7-A-20) Then save the file and exit your text editor.
If you are using graphics files (DOORSG) as well as
ASCII text files (DOORS), you might also edit the
graphics file now. Press F3 to edit the DOORSG
file.
7-A-21) When you leave your editor, you are returned to the
Main Board Configuration screen. Press ESC twice
to exit PCBSetup. You are now asked if you wish to
save your configuration.
7-A-22) Save your configuration. You may use "Q" for
Quick-save, so that PCBoard does not spend a long
time performing checks on your conference
structure.
You have now completed the operations necessary to let PCBoard
know how to find and manage the RoseMail Door, so you may press
ESC to exit the PCBoard System Manager.
One more major step remains to complete your installation of the
RoseMail Door: this step is to use the RoseMail System Manager to
tell your system about RoseMail.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 35
8) RM.EXE: The RoseMail System Manager.
If you are running multiple nodes under a network, make sure
you are logged onto your network drive. If you are running a
single-node system, or multi-tasking on a single machine, log
onto the drive where you keep your PCBoard program files.
Change to your RoseMail program directory (usually:
C:\PCB\ROSE), and run RM.EXE while logged onto this directory.
8-A) Select File Paths from the main menu.
8-A-1) Enter the name of a text editor to use to edit the
ASCII help files.
8-A-2) Enter the name of an ANSI editor to use to edit the
ANSI help files.
8-A-3) Rmail Directory: Usually, C:\PCB\ROSE. This is your
RoseMail program directory, the one where you keep
your RoseMail EXE files, your ROSEMAIL (keyword) file,
your standard RoseMail configuration file (RMAIL.DAT)
which you create the first time you configure
RoseMail, and your ROSEMAIL.KEY file if you are
registered. If you are running a multi-node system,
all your nodes from which RoseMail is run will access
this directory.
8-A-4) Enter the path and filename for the file CONFDATA.DAT,
which tracks your conference flags and network
translations. This file must go in a location where
it can be shared, as it is used by all nodes. We
therefore recommend that you place it in your RMAIL
directory (the program directory), which would usually
be C:\PCB\ROSE.
NOTES on File Paths for PCBOARD.DAT, PCBOARD.SYS & USERS.SYS
------------------------------------------------------------
See the Guided Tour at the beginning of this guide for notes and
examples concerning the configuration of file paths for
PCBOARD.DAT, PCBOARD.SYS, USERS.SYS, and the Work Directory. An
abbreviated description of how to configure File Paths follows
here.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 36
All sysops
----------
If you are following the directory structure indicated so far
in this guide, you can leave the default configuration for File
Paths just as it comes with your RoseMail files, because the
files PCBOARD.DAT, PCBOARD.SYS and USERS.SYS will normally be
found in the caller's current directory (the node directory).
By default, no drive or pathnames are indicated in the File
Paths for these three files.
Single-node sysops
------------------
Single-node sysops may treat the phrase "for the current node"
in the instructions for configuring the File Paths as meaning
"for Node 1". Check the Guided Tour at the beginning of this
guide for detailed information.
8-A-5) Enter the name and location of the PCBOARD.DAT file
for the current node. Usually, you will enter only
"PCBOARD.DAT".
8-A-6) Enter the name and location of the PCBOARD.SYS file
for the current node. Usually, you will enter only
"PCBOARD.SYS".
8-A-7) Enter the name and location of the USERS.SYS file for
the current node. Usually, you will enter only
"USERS.SYS".
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 37
8-A-8) Enter a directory name for RoseMail to use as a work
area. This directory will be deleted each time a
caller exits the door. Each node must have a work
directory distinct from that of any other node. You
may use "#" or "%PCBNODE%" in the directory name, to
have RoseMail substitute the node number for the
variable (# or %PCBNODE%), thus providing a
distinctive name for each work directory. If you are
following the recommendations in this guide, you can
use the default, "C:\PCB\WORK#", and change only the
drive letter if your PCBoard program directory resides
on a drive different from C.
Note: This is the location RoseMail uses to generate
mail packets, which is why each node must have its
own separate work directory.
NOTE: See the main reference section under "File Paths" for
detailed examples of File Path configuration, including those that
list only the filenames for PCBOARD.DAT, PCBOARD.SYS and
USERS.SYS, so as to access a current (node) directory, and for
examples of configurations that use DOS environment variables, as
set by PCBoard 14.5a or by you in AUTOEXEC.BAT or BOARD.BAT.
The remainder of this section is a quick summary of points made
in the main reference section, below. Consult that section if
you have questions.
Now you may exit the File Paths menu, and configure any of the
other items from the main menu. The defaults come with PKZIP
and PKARC defined as compression programs, and DSZ defined in
Transfer Protocols. If you use these programs, you will
probably not need to configure these areas right away. You can
customize them for your system later, if they do not work as
you wish them to when you test them.
You can leave the Transfer Rates/Limits set at the defaults for
now.
Configure Local Board Information. If your version of RoseMail
is not registered, fill in the name of your system and the
other fields at the top of this menu.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 38
In the submenu for Duplicate checks, to block the posting of
duplicate messages, change the default "N" to a "Y" in either
or both of the fields shown. You should build the RDX files
now if you are installing RoseMail for the first time. If you
are installing RoseMail now, or upgrading from an earlier
version of RoseMail, use your down arrow to get to the last
item on the menu, and press Enter to build or rebuild the RDX
files. Also on this menu, check the number of RoseNet messages
for which you wish to track duplicates, and change the default
(2000) if you wish.
Configure the Options area. Use the information boxes on the
screen or the main reference section of this guide to assist
you. Consult the main reference section if you need additional
help.
Configure the RoseNet Information area. The online help should
get you through this area quickly. You can leave most or all
settings at their defaults. If you wish further assistance,
consult the main reference section.
If you are setting up for network mail right away, and you have
installed a ROSEMAIL.KEY file, configure the Networks/NetMail
area for any networks you are currently carrying. You may omit
the last two items on the menu, Pointer Resets and USERS.INF
reset. Configure the others. Remember to use the Main
Reference section of this guide to assist you if you need help.
The information boxes at the bottoms of the screens may be
sufficient to help you through these menus.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 39
If you are acting as a host for other RoseMail sysops, have
them give you their addresses, or "Host Names," which are
listed in their Available Networks screens. The term "Address"
applied to versions of RoseMail previous to 2.00. With 2.00,
the term has changed to "Host Name", which consists of the last
four digits of the sysop's RoseReader for Sysops serial number.
All RoseMail sysops have a copy of RoseReader for Sysops -
either a full Platinum version, which will read QWK packets, or
RoseReader for Sysops Lite, which has the Sysop Module
capabilities but omits the QWK packet reader. Enter the Host
Names in your Net Sysop Access submenu. You will find this
submenu under the Available Networks menu. If you are a net
sysop and you are using RoseMail on your hub, ask your hub
sysop to enter your Host Name in the Net Sysop Access
configuration area on the hub. Do NOT enter your own Host Name
(in your own user record on your own system) in this submenu;
if you enter it here, you will encounter unpredictable results.
Leave the address or Host Name in your own record blank
(zeros).
If you are acting as a host to sysops who do not use RoseMail,
enter their Host Names as a "non-RM" address. To do this, use
your Up Arrow to reach the Host Name field, and then press
Ctrl-Y to delete the information in the field. Yes, delete
those zeros. When you move your cursor off the field, it will
change to "non-RM," which is a sufficient Host Name for sysops
who are not running RoseMail.
If you plan to carry many netmail conferences, and you are
installing RoseMail for the first time, and you do not now have
a QWK-compatible mail door on your system, your longest session
will be filling in the Network Translations, where you match
your own conference numbers to those of your hubs. You would
do well to work from a written list, and to check all typed
numbers carefully, so that you do not end up dumping messages
into the wrong conferences.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 40
If you already have a Qmail-compatible mail door on your
system, try the conversion program for the network translation
table that comes with RoseMail 2.00. This program will convert
the network translation table, where you match your conference
numbers to those on your hub, to RoseMail's format. It will
work with most Qmail and compatible mail doors. As with any
other operation of this sort, you should make sure, before you
write over any working files, that you have copies of your
working files somewhere else, so that if the operation goes bad
on your system, you can retrieve the originals.
When you have finished configuring the Networks/NetMail area,
Exit and Save your configuration. This action will create a
file called RMAIL.DAT. RMAIL.DAT will be located in your
\PCB\ROSE directory (or whatever you called your Rmail
Directory).
Configure the Conference Data area as you wish. The
information boxes at the bottoms of the screens will assist
you. Consult the Main Reference section of this guide if you
need assistance.
Configure the User Flags area as you wish. Check particularly
your own user record, and that of any co-sysops or conference
sysops.
If you wish to provide Add-In Files or Magazines right from the
start, refer to the main reference section of this guide if you
need to. Otherwise, the online Tickler help will assist you.
Select Conference Optimize, and press Enter, to create the
OPT.LST file.
If you are running a single-node system, your RoseMail is now
configured enough so that your RoseMail Door, your net exchange
software, and your RoseNet mail system are all active. It
would be wise to run a few tests with it, to check your
configuration. You can log on locally to do this, and have a
friend call in as well. Make sure you perform tests to
determine that all your conference configurations are correct.
You can send a carefully-planned REP packet to your hub,
containing only one message in each conference, and then go
online at your hub to check whether the correct messages
arrived in the correct conferences, using PCBoard's Quickscan,
and capturing the messages.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 41
If you are running a multi-node system, you should test your
configuration on the main node first. If you find errors,
consult the main reference section to help you fix them. It is
easy to return to the RoseMail System Manager (RM.EXE) to make
corrections to your RMAIL.DAT and related global files (such as
CONFDATA.DAT).
Once you have RoseMail running smoothly on your main node,
assuming you have followed the instructions in this guide, it
should operate for all nodes that share the C:\PCB\ROSE
directory (or its equivalent). If you wish to make one or more
special configurations for individual nodes, refer to Step 9
toward the end of the Main Reference section of this guide.
You may check the installation for your other nodes as follows.
MULTI-NODE SYSTEMS: Checking a global RoseMail installation
------------------------------------------------------------
If your RoseMail is registered, check that you have copied your
ROSEMAIL.KEY file to C:\PCB\ROSE (or its equivalent, that is, the
directory where RMAIL.DAT already exists).
Check that the files required by PCBoard for operating other nodes
are in place as necessary (in your node directories). Consult the
PCBoard manual for details.
If you are running PCBoard 14.5 rather than 14.5a, and you have
used DOS environment variables in the File Paths configuration,
make sure that your BOARD.BAT (or AUTOEXEC.BAT) for each node sets
the variables as specified in the File Paths configuration. Edit
your BOARD.BAT (or AUTOEXEC.BAT) files to set these variables if
necessary.
This completes your initial installation. Consult the main
reference section for further information. It would be a good
idea to make an interim backup of your current installation now.
If you are going to make a special configuration for a node or
nodes, see Step 9 in the Main Reference section.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 42
ROSEMAIL MAIN REFERENCE
-----------------------
GENERAL INFORMATION
-------------------
What you need to know
---------------------
Assumed: You know DOS
----------------------
It is assumed that you have a basic knowledge of DOS commands.
If you have difficulty, please consult your DOS manual. Simple
DOS terminology is used throughout this guide.
Assumed: You know your network software
----------------------------------------
It is assumed that if you are running a multi-node BBS, you are
familiar with the structure of the network or multi-tasking
software you are using, and can manage it without problems. If
you have difficulty, please consult the manual for your network
or multi-tasking software.
Assumed: You know the PCBoard software
---------------------------------------
It is assumed that you are fairly intimately familiar with the
PCBoard software and how it operates on your BBS, particularly
in relation to messages. PCBoard procedures are covered here
only as they relate to RoseMail, so if you have questions about
PCBoard, please consult your PCBoard manual.
The intent of this guide, however, is to allow you to install
RoseMail with relative ease even if you are a brand-new sysop
who has never seen PCBoard up close before. If your PCBoard is
properly installed, you should have no difficulties installing
RoseMail, providing you follow the instructions contained here.
But if you find this guide confusing or inadequate, or if you
have suggestions, please notify us so we can improve it.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 43
CONVENTIONS used in these instructions
--------------------------------------
For simplicity in communicating, this guide assumes:
Your PCBoard program files are in C:\PCB
Your RoseMail program files will go in C:\PCB\ROSE
Therefore: Where your drive or directory names are
different, please substitute the names that apply to
your own system for those used here.
You are using DSZ for your protocols, and DSZ.COM (or
.EXE) is located in the C:\PCB directory.
Therefore: If you are using some protocol program other
than DSZ, or if your DSZ is in a directory other than
C:\PCB, please substitute your own directory names, or
the appropriate instructions for installing protocols,
for those given here.
Exceptions to flexibility in directory names
--------------------------------------------
RoseMail depends on having the subdirectory name "\TEXT" off
its program directory, in order to find its .TXT files. So if
your RoseMail program directory is C:\PCB\ROSE, name your
.TXT file directory C:\PCB\ROSE\TEXT. There are several
other subdirectories you may need to make under C:\PCB\ROSE;
these are mentioned in the appropriate places in the guide.
RoseMail itself will make other subdirectories and create
files as needed.
Each node on your system MUST have a unique RoseMail Work
Directory. You do not create this directory yourself, but
you specify its drive, path, and filename in the File Paths
configuration when you use the RoseMail System Manager
(RM.EXE). Read the Guided Tour at the beginning of this
guide for details.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 44
Terminology used in this guide
------------------------------
BBS.QWK and BBS.REP
-------------------
In this guide, we have used the generic "variable" names
for caller's mail packets "BBS.QWK" and "BBS.REP." When
you see these, you should substitute the appropriate
packet name for the "BBS" part of the filename. The name
you substitute would normally be the packet name you use
for your own BBS.
HUB.QWK and HUB.REP
-------------------
When discussing netmail, we have substituted for the "BBS"
part of this filename "HUB", to identify a .QWK or .REP
packet that is transferred between sysops for the purpose
of exchanging echo mail packets. So, a netmail .QWK is
called a "HUB.QWK," and a netmail .REP is called a
"HUB.REP" in this guide. Remember to substitute your
hub's packet names for the "HUB" part of "HUB.QWK" and
"HUB.REP".
Screen simulations
------------------
In the screen simulations, the limitations of imitating a
computer screen with a text file or printed page apply.
The screens you see on your computer will probably differ in
detail from those simulated in this guide. Those shown here
merely illustrate the principles of configuration. For
instance, you should substitute your own drives and
directories, files, command lines, or any other configurable
items, for the ones illustrated here.
In screen simulations, where a selection is shown, the
symbols "<==" or "==>" show the location of the cursor
highlight bar. Make sure to distinguish these from symbols
at the top of the simulated screen that suggest you can press
TAB or Shift-TAB to scroll to the right or left of the
screen. Context should serve to distinguish them.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 45
ORIENTATION to the task
-----------------------
When you install RoseMail, you go through from eight to nine
initial steps. If you configure one or more nodes
differently from your global configuration, you will have a
ninth step to complete, to edit the ROSEMAIL (keyword) file
to branch to your special configuration file (RMAIL.DAT), and
to run the RoseMail System Manager to create or edit that
configuration file.
The steps you will take to install and configure RoseMail are
listed below, and are described fully in the next section.
1) BACKUP! Back up your system!
2) SYSTEM CONFIGURATION: You need a setting of at least
FILES=25 in your CONFIG.SYS to run RoseMail.
3) SUBDIRECTORIES: Make subdirectories to hold your
RoseMail files.
4) EXTERNAL PROTOCOLS: Make sure RoseMail will be able
to find DSZ (or any other external protocol you
install).
5) DOOR LOCATION and SECURITY LEVEL: Decide on a door
number for RoseMail, and choose a minimum security
level for callers to use it.
6) COPY FILES: Copy files to RoseMail directories.
7) PCBSM: PCBoard System Manager: Tell PCBoard about
RoseMail.
8) RM.EXE: RoseMail System Manager. Tell RoseMail how
it should run on your system.
9) SPECIAL CONFIGURATIONS (multi-node systems only): If
you wish to configure RoseMail to operate differently
on one or more of your nodes, read and follow the
instructions for special configurations at the end of
this section.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 46
INSTALLING ROSEMAIL
-------------------
Initial steps to take
---------------------
1) BACKUP: Back up your system!
1-A) Back up your system.
Back up your system. When you install RoseMail,
PCBoard makes changes to your USERS and USERS.INF
files. If you are a Nervous Sysop, it would not hurt
to make an additional extra copy of these two files on
floppy disks before you begin, so that if the sky
falls down at the instant these two files change, you
can recover them even if your backup got crushed.
2) SYSTEM CONFIGURATION: Check your CONFIG.SYS file.
2-A) If you do not have a statement that says
FILES=nn
where "nn" is a number, then add one to your
CONFIG.SYS, using a text editor. You must set "nn" to
a value of at least 25 for RoseMail to run. This
number represents the number of files that DOS and the
program(s) you are running can hold open at any one
time. For example, then, you could add the statement
FILES=25
to your CONFIG.SYS. It does not much matter where in
CONFIG.SYS you put this statement, but you might put
it close to any BUFFERS= statement you may have.
If you already have a FILES=nn statement, and the
number is less than 25, change the number to 25.
Now, if you have added a FILES= statement, or if you
have changed an existing one, save your new
CONFIG.SYS, and then reboot your system so the
FILES=25 (or more) statement will take effect.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 47
3) SUBDIRECTORIES: Make subdirectories to hold RoseMail
files.
IMPORTANT! If you are running a multi-node system under
a network, RoseMail must be installed on a network
drive.
3-A) Log onto your network drive, or if you are running
only a single machine or a single node, onto the
drive where you keep your PCBoard program files.
You will be creating subdirectories for files that
are common to all nodes on your system.
3-B) Make a subdirectory off your \PCB directory to hold
the RoseMail .EXE files.
Usually: MD \PCB\ROSE
3-C) Make a subdirectory off the one you just made, and
call it \TEXT. Note: this subdirectory must be
named "\TEXT", and it MUST be off your \PCB\ROSE
(RoseMail program) directory, so that RoseMail can
find its Help and menu text files.
Usually: MD \PCB\ROSE\TEXT
3-D) If you are planning to carry Magazine files, make a
subdirectory to hold them.
Usually: MD \PCB\ROSE\MAG
3-E) If you plan to carry Add-In files, you may make a
separate subdirectory in which to keep them.
For instance: MD \PCB\ROSE\ADDIN
3-F) If you will use Direct Mail, the RoseNet routed,
registered mail system, make a subdirectory to hold
the routing information and MAP files.
Usually: C:\PCB\ROSE\DM
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 48
4) EXTERNAL PROTOCOLS: If you plan to use external
protocols such as DSZ, make sure RoseMail will be able
to find the appropriate programs. We use DSZ as the
main example here. If you are going to select
RoseMail's internal protocols, you may skip this
section, and go on to the section on the Transfer
Protocols screen.
RoseMail 2.00 contains a set of internal protocols, so
as to be compatible with non-standard com ports.
Previous versions of RoseMail depended on your
installing external protocols. We use Chuck Forsberg's
DSZ here as the main example for how you would set up
external protocols. You will need to register your DSZ
to have it work fully with RoseMail. You may install
other protocols, too. Instructions given here are for
installing DSZ, and an example of how to install HS/Link
is given. Use similar principles to install other
external protocols.
If DSZ is already in your DOS path, you may go on to the
next step (Step 5). If DSZ is not already in your DOS
path, you can choose one of the three alternatives
listed here:
(1) Usually recommended: Set the DOS path to include
the drive and directory where DSZ is already located.
You can do this in AUTOEXEC.BAT or BOARD.BAT.
(2) Copy DSZ.COM (or DSZ.EXE) to a directory that is
in your DOS path. Do not erase the original unless
you are sure PCBoard can find your new copy, or your
callers may let you know they are having difficulty
with their file transfers from your PCBoard.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 49
(3) Recommended if you are running more than one node
on the same machine, for instance, by using DESQview:
Add the drive and path for DSZ to the RoseMail
Transfer Protocols command lines, using the Transfer
Protocols configuration submenu in the RoseMail System
Manager. Instructions for doing this are given under
Transfer Protocols, below. However, if you have only
one node on any one machine, space limitations (40
characters) on the Transfer Protocol command lines
suggest that you might find either of the previous two
choices more suitable to your system than this one.
If you choose alternative (1) above, and use AUTOEXEC.BAT
or BOARD.BAT to hold the necessary path statement, you may
change your AUTOEXEC.BAT or your BOARD.BAT appropriately
now. If you make the change in AUTOEXEC.BAT, do not
forget to run your AUTOEXEC.BAT to have the new path
instruction take effect.
If you choose alternative (2) above, this is a good time
to copy your DSZ.COM (or DSZ.EXE) to the directory that is
in your DOS path.
If you choose alternative (3) above, you may delay
altering the Transfer Protocol command lines until you
reach the Transfer Protocols section of this guide, where
instructions are provided.
If you are planning to install HS/Link, see the examples
of command lines for this protocol in the Transfer
Protocols section, below.
5) Choose DOOR NUMBER and SECURITY LEVEL.
5-A) Decide in what door (number) you will install
RoseMail.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 50
5-B) Decide on the minimum security level you will
require for callers to use RoseMail.
If you plan to add a new security level for
RoseMail, consult your PCBoard manual for
assistance if you need it. Make sure the PCBoard
configuration is complete for the new security
level. You will alter your PWRD file as necessary,
and you may need to alter or add to certain text
files as well, particularly if you use
security-specific menu files (BRDM, for example).
6) COPY FILES:
6-A) Collect your RoseMail files. Your filenames may
begin with "!"; however, we are omitting the "!"
here to make the filenames easier to read.
RM170A.ZIP
EXE files for 80286 machines and up (with some
information in text files as well)
RM170B.ZIP
EXE files for 8088 or 8086 machines (with some
information in text files as well)
RM170C.ZIP
RoseMail's menu and help files (*.TXT)
RM170D.ZIP
Text and information files, including this guide,
the Caller's Guide To RoseMail, and the RoseMake
User's Guide.
RM170E.ZIP
Magazine sample files
ROSEMAIL.KEY
Registered versions only (download from Rose
Media BBS's REGISTER door).
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 51
6-B) Unzip RM170A.ZIP (but if you are installing on an
8088 or an 8086 machine, use RM170B.ZIP instead).
Now copy RM.EXE and ROMAIL.EXE to your RoseMail
directory.
Usually, copy these files to: C:\PCB\ROSE
6-C) If you have registered RoseMail, you have a file
called ROSEMAIL.KEY. Copy it to this same
subdirectory (C:\PCB\ROSE or its equivalent) now.
6-D) Unzip RM170C.ZIP, and copy all the .TXT files to
C:\PCB\ROSE\TEXT (or to the \TEXT subdirectory you
made in step 3-C above).
Usually, copy the files to: C:\PCB\ROSE\TEXT
6-E) If you are going to carry the sample Magazine
files, unzip RM170E.ZIP, and copy the files to your
Magazine subdirectory.
Usually, copy the files to: C:\PCB\ROSE\MAG
6-F) If you are going to use the Direct Mail, RoseNet,
system, unzip DM.ZIP and copy the files into your
Direct Mail directory.
Usually, copy the files to: C:\PCB\ROSE\DM
7) PCBSM: PCBoard System Manager.
In this step, you forge the links between PCBoard and
RoseMail. Consult your PCBoard manual for any
information you may need about PCBoard that is not
included here.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 52
7-A) INSTALL ROSEMAIL as a Third Party Application in
PCBoard
NOTE: If this is your first installation of
RoseMail, you will install only one node to start
with. If all your nodes will share the same
configuration (RMAIL.DAT file), installing RoseMail
on Node 1 will give access to all nodes, assuming
your DOORS.LST (PCBSetup, Main Board Configuration)
is edited as recommended in this guide.
Instructions for making special configurations for
individual nodes are presented near the end of the
section on the RoseMail System Manager.
IMPORTANT! If you are running a multi-node system,
under a network, RoseMail must be installed on a
network drive. So make sure you are working off
your network drive.
7-A-1) !!! WARNING !!! TAKE ALL NODES DOWN!
No node may be running PCBoard when you use PCBSM
to modify the USERS.INF file. The USERS.INF file
is changed when you install a Third Party
Application. Make sure, too, that you have not
turned a node off while PCBoard was running on
it.
Make sure you have backed up your system.
If you have backed up your system, and all nodes
are down, you are ready to run the PCBoard System
Manager.
7-A-2) Start the PCBoard System Manager.
7-A-3) Select D, User Info File Maintenance, from the
main menu.
7-A-4) From the User Info File Maintenance menu, select
C, Add/Update Third Party Application.
7-A-5) When you are asked to enter the name of the Third
Party Application, enter "ROSEMAIL" (do not type
the quote marks).
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 53
7-A-6) When you are asked for Version, Static Size,
Dynamic Size, and keyword, enter the following
information:
Version: 1
Static Size: 256
Dynamic Size: 1
Keyword: ROSEMAIL
NOTE: for the "Version" number, do NOT put in the
minor version number (such as "1.70" - it is the
MAJOR version number ("1") that is required here.
7-A-7) Now press PgDn to let PCBoard modify the
USERS.INF file.
The information you have just entered will now
be written to disk.
7-A-8) You may find that another screen pops up asking
you to enter another Third Party Application
name. If this happens, press ESC to exit.
7-A-9) Press ESC to return to PCBSM's main menu. Now
select C, PCBSetup.
7-A-10) Select J, Main Board Configuration.
7-A-11) Highlight the DOORS.LST file, toward the lower
right side of the screen.
7-A-12) Press F2 to edit DOORS.LST.
7-A-13) Edit DOORS.LST, as follows:
7-A-13-a) Door Number: Press Alt-I to create a new
line. This will make a new door number
for you. Place your cursor beside the
door number you have chosen for RoseMail.
7-A-13-b) For the Filename, enter ROSEMAIL.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 54
7-A-13-c) Password: If you are going to require a
password for callers to open the RoseMail
Door, enter it in this field. This is a
single password of your choosing, and it
applies to all callers. If you do not
require a password for callers to access
RoseMail, leave this field blank.
7-A-13-d) For the Security Level ("Sec"), enter the
minimum security level your callers will
require in order to use your RoseMail
Door.
7-A-13-e) Specify "N" under Login, unless you want
your callers to be forced into RoseMail
immediately following logon.
7-A-13-f) In the "USER.SYS" column, enter Y.
7-A-13-g) In the "DOOR.SYS" column, enter N.
7-A-13-h) In the "Shell" column (if there is one),
enter N.
NOTE: Some versions of PCBoard may not
show the "Shell" column, since the Shell
Door is new with PCBoard version 14.5a.
7-A-13-i) In the "Path to DOOR Files" column, enter
C:\PCB\ROSE (or its equivalent on your
system). Your "DOOR" (ROSEMAIL, or
KEYWORD) file will go into the
subdirectory you specify here, which is
your RoseMail program directory.
Now, from this menu, you may edit (create)
your DOOR ("keyword") file, that is, the
file called ROSEMAIL. Notice that this
filename has no extension.
Check the Guided Tour at the beginning of
this guide for detailed information on how
PCBoard turns this file into DOOR.BAT when
the caller runs RoseMail.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 55
7-A-14) Highlight the filename "ROSEMAIL", and press
F2 once more, to "edit the DOOR file"
(ROSEMAIL).
Your text editor now loads, to let you create
the ROSEMAIL file. When typed, the file
should look like this (change the drive and
subdirectories specified, if necessary):
C:\PCB\ROSE\ROMAIL
BOARD
7-A-15) When you have finished typing your ROSEMAIL
file, save it, and exit your text editor.
When you do this, you are returned to the
"Edit DOORS file" menu of the PCBoard Setup
Utility.
7-A-16) Press ESC to return to the Main Board
Configuration menu of the PCBoard Setup
Utility. You will be asked if you wish to
save the new configuration.
7-A-17) Save the new configuration.
7-A-18) Edit the DOORS file
The DOORS file is the list your callers see
when they type "DOOR" or "OPEN" and press
Enter at the PCBoard Command prompt.
The DOORS file listing is in the lower left
area of the Main Board Configuration screen,
under "Menu Listing." Press your Up Arrow to
highlight the DOORS file, and press F2 to edit
it.
If you have one or more doors installed
already, your DOORS file will probably little
resemble the following:
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 56
Screen 1. The DOORS file.
┌────────────────────────────────────────────────────────────────┐
│ │
│ Door # Name Description │
│ ============================================================== │
│ │
│ 1 DorMouse Pet Door for LogiTech & MicroSoft Meese │
│ │
│ Special Access Level required for │
│ Felines. Rats, please use the TrapDoor. │
│ Canines allowed only by Feline Invitation │
│ │
│ 2 │
│ │
└────────────────────────────────────────────────────────────────┘
7-A-19) Type the information your callers will need,
showing the Door Number, the Name (RoseMail),
and a brief description of RoseMail for your
callers. For example:
Screen 2. Description of RoseMail for Callers.
┌────────────────────────────────────────────────────────────────┐
│ │
│ Door # Name Description │
│ ============================================================== │
│ │
│ 2 RoseMail Offline Mail and other Services │
│ │
│ Callers who have the Platinum version of │
│ RoseReader will find additional features │
│ available, such as unattended │
│ communications, file downloads and │
│ uploads, magazines. │
│ │
└────────────────────────────────────────────────────────────────┘
7-A-20) Then save the file and exit your text editor.
If you are using graphics files (DOORSG) as
well as ASCII text files (DOORS), you might
also edit the graphics file now. Press F3 to
edit the DOORSG file.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 57
7-A-21) When you leave your editor, you are returned
to the Main Board Configuration screen. Press
ESC twice to exit PCBSetup. You are now asked
if you wish to save your configuration.
7-A-22) Save your configuration. You may use "Q" for
Quick-save, so that PCBoard does not spend a
long time performing checks on your conference
structure.
You have now completed the operations necessary to let PCBoard
know how to find and manage the RoseMail Door, so you may press
ESC to exit the PCBoard System Manager.
One more major step remains to complete your installation of the
RoseMail Door: this step is to use the RoseMail System Manager to
tell your system about RoseMail.
THE ROSEMAIL SYSTEM MANAGER
---------------------------
GENERAL INFORMATION
-------------------
Registering RoseMail: If you have just registered RoseMail, and
have already installed the Test Drive version, see the section
near the end of this guide, entitled "UPGRADING your ROSEMAIL",
for information on how to install your ROSEMAIL.KEY file and
update your RMAIL.DAT. Make sure you read the SETUP.170 file and
the WHATSNEW.170 file to ensure that you complete all necessary
steps to upgrade your RoseMail.
If you have configured your RoseMail before, make sure you know
where your RMAIL.??? file is located and what its full
<filename.ext> is. If you are not sure, check the section near
the end of this guide called "IN CASE OF DIFFICULTY".
Planning Your System
--------------------
Here are some considerations that may affect your system's
efficiency.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 58
Planning the location of the configuration file RMAIL.DAT
---------------------------------------------------------
RoseMail keeps your global RoseMail configuration information
(for all nodes except those configured specially) in a file
called RMAIL.DAT. This file is updated each time you run the
RoseMail System Manager (RM.EXE) and save your new
configuration. RMAIL.DAT is saved in your current directory -
that is, in the directory you are logged onto when you run the
RoseMail System Manager.
The simplest way to configure RoseMail is to place RoseMail's
global configuration file (RMAIL.DAT) in the same directory to
which you copied ROMAIL.EXE and RM.EXE (usually, C:\PCB\ROSE).
We recommend strongly that you configure RoseMail this way. To
do this, log onto C:\PCB\ROSE (or whatever you named this
directory), and type "RM" to start the RoseMail System Manager.
This procedure will place RMAIL.DAT in C:\PCB\ROSE (or whatever
you named this directory).
With RoseMail 2.00, a new file called CONFDATA.DAT supplements
RMAIL.DAT. CONFDATA.DAT contains your conference flags (from
Conference Data), and your network translation tables.
CONFDATA.DAT should normally be kept in the same directory as
RMAIL.DAT. During your configuration, you will be asked to
provide a drive, path, and filename for CONFDATA.DAT, and we
recommend that you use your system's equivalent of
C:\PCB\ROSE\CONFDATA.DAT for this file.
Notes for multi-node sysops: the RMAIL.DAT that is in
C:\PCB\ROSE (or its equivalent) is a "standard" or "global"
version accessible to all nodes. If you configure one node or
more in a special way, different from your standard
configuration, you need to create a different RMAIL.DAT file
and place it in the directory for the node you are configuring.
You may, if you wish, give this file a different extension (for
example: RMAIL.21 for Node 21) so as to identify it easily.
See the Guided Tour at the beginning of this guide for a
detailed explanation.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 59
To create a special RMAIL.DAT file, you can log onto the node
directory concerned, and run RM.EXE (the RoseMail System
Manager) from there. Your commands for running RM.EXE might
then look like one of these:
cd\pcb\node21
c:\pcb\rose\rm rmail.21
OR
c:\pcb\rose\rm c:\pcb\node21\rmail.21
In other words, by specifying on the command line the
particular RMAIL.??? file that you wish to work with, you avoid
writing over your standard (global) RMAIL.DAT by mistake. You
may also specify your standard RMAIL.DAT file on the command
line when you wish to make certain it is that file you wish to
work with:
c:\pcb\rose\rm c:\pcb\rose\rmail.dat
If you have special configurations for one or more nodes, your
ROSEMAIL (keyword) file will need branches. See the
description of the ROSEMAIL file branches, under the heading
"SPECIAL CONFIGURATIONS FOR INDIVIDUAL NODES", near the end of
this guide, for details.
To assist you with the RoseMail System Manager, here is is list of
editing keys.
Table 1. RoseMail System Manager: List of Editing Keys
--------------------------------------------------------
ENTER - select a submenu
ESC - return to previous menu
TAB - move to next field
Shift-TAB - move to previous field
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 60
Arrow keys
----------
Right Arrow - move one character to the right
Left Arrow - move one character to the left
Up Arrow - move up one line
Down Arrow - move down one line
HOME - Cursor to beginning of field
END - Cursor to end of field
Backspace - Delete character to left of cursor
Delete - Delete character under cursor
PgDn - Move down one screen
PgUp - Move up one screen
Insert - Toggle Insert Mode (ON or OFF)
NOTE: When Insert Mode is toggled ON, the cursor
becomes large; when it is off, the cursor appears as an
underline.
Ctrl-Y - delete the contents of the current field
Ctrl-U - restore the previous contents of the current
field (providing you have not moved the cursor
out of the field)
The following keys apply to the following areas:
a) User Flags
b) Conference Flags
c) Conference Ownership (under Networks/NetMail)
Ctrl-J - ask for, and then jump to, a given conference
number
Ctrl-S - ask for a low conference and a high conference
and then set the current flag. That is, if
you were in the conference flag column 5, and
you press Ctrl-S, you would set flag 5. If
you were on network #17, you would set the
conference ownership to 17 for the range low
to high (inclusive)
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 61
Ctrl-C - same as Ctrl-S but clears the flags instead of
setting them
These last three key combinations (new with RoseMail 1.70) will be
particularly appreciated by sysops who have hundreds or thousands
of conferences for which to specify settings. Even if you have
fewer, using these keys will help you avoid missing a setting for
a conference or two, so we recommend using them.
List of editing functions
-------------------------
Select a Submenu
----------------
To select a submenu, highlight it with the cursor bar, and
press Enter.
Leave a Submenu
---------------
To leave a submenu and return to the previous menu, press
ESC.
Scroll Screen
-------------
Press PgDn to move to the next screen down.
Press PgUp to move to the next screen up.
Move to Next Field
------------------
To move to the next field in a submenu, press TAB. The
Arrow keys will also move you through some of the fields.
Move to Previous Field
----------------------
To move to a previous field in a submenu, press Shift-TAB.
The Arrow keys will also move you through some of the
fields.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 62
Move to Beginning of Field
--------------------------
Press HOME to move to the beginning of the field you are
editing.
Move to End of Field
--------------------
Press END to move to the end of the field you are editing.
Toggle Insert Mode
------------------
Insert Mode is OFF by default. The INSERT key will
"toggle" Insert Mode ON and off again. When Insert Mode
is ON, the cursor becomes large. When it is off, the
cursor appears as an underline.
Edit information in a field (edit what is already there)
--------------------------------------------------------
If you press the Right or Left Arrow key in a field BEFORE
you type anything, you can edit the field without erasing
what is already there.
A TIP: Combine pressing an arrow key before typing
anything with toggling Insert Mode to make your editing
easy.
Edit information in a field (erase what is already there)
---------------------------------------------------------
If you start typing in a field that already contains
information, the previous contents of the field will
disappear, and the new information you type will appear.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 63
Restore previous information in a field
---------------------------------------
If you have typed into a field and find you want to
restore the previous contents, you may press Ctrl-U (for
"Undo"), providing you have not moved the cursor out of
the field.
Once you move the cursor to another line or another field,
you cannot restore the previous contents, other than by
exiting the RoseMail System Manager without saving your
configuration.
Delete all information in a field
---------------------------------
If you wish specifically to delete the information
currently contained in a field, press Ctrl-Y to do so. As
long as you do not move your cursor out of the field, you
can restore the previous contents by pressing Ctrl-U.
Exit without saving your configuration
--------------------------------------
To exit without altering your previous RMAIL.DAT file,
answer "N" to the question about saving your
configuration.
Save your configuration
-----------------------
To save your configuration, select Exit from the Main
Menu, and answer "Y" to the question about saving the
configuration.
Flag-setting keys: set or clear multiple flags
-----------------------------------------------
When setting or clearing flags in the categories User
Flags, Conference Flags, and Conference Ownership (under
Networks/NetMail), use the following keys to assist you.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 64
Ask for and jump to a specified conference number
-------------------------------------------------
With your cursor in the flag column you are configuring,
Ctrl-J will prompt you for a conference number (or user
flag), and then jump to it.
Set flags for a range of conferences
------------------------------------
With your cursor in the flag column you are configuring,
Ctrl-S will prompt you for a range of conferences, low
to high, and then set the selected flag for that range
of conferences.
Clear flags for a range of conferences
--------------------------------------
With your cursor in the flag column you are configuring,
Ctrl-C will prompt you for a range of conferences, low
to high, and then clear the selected flag for that range
of conferences.
CONFIGURING WITH THE ROSEMAIL SYSTEM MANAGER
--------------------------------------------
If you are configuring RoseMail for the first time, or if you are
changing a standard (global) configuration, log onto your network
drive (or the drive where you copied the ROMAIL.EXE and RM.EXE
files). That is, if your shared program directory C:\PCB\ROSE (on
your network drive) is not now your current directory, log onto it
before continuing. This will ensure that the RoseMail System
Manager's configuration file, RMAIL.DAT, gets saved in the
C:\PCB\ROSE (or equivalent) directory.
If you are making (or changing) a special configuration, log onto
the directory where you plan to (or did) store that configuration,
and start RM.EXE from there. If you changed the RMAIL filename to
reflect the node it is for, make sure you specify the correct
filename on the command line (for example, "RMAIL.3"). Doing this
will ensure that the copy of RMAIL.DAT (or RMAIL.???) you create
or change is the one corresponding to the node you are
configuring.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 65
Now you are ready to configure your system using the RoseMail
System Manager (RM.EXE).
Orientation to configuring RoseMail
-----------------------------------
This section is written as though you are installing RoseMail for
the first time. Its content, however, applies equally to any
changes you may wish to make later.
To configure RoseMail for the first time
----------------------------------------
8) RM.EXE: If you are running multiple nodes under a
network, make sure you are logged onto your network drive.
If you are running a single-node system, or multi-tasking
on a single machine, log onto the drive where you keep
your PCBoard program files. Change to your RoseMail
program directory (usually: C:\PCB\ROSE), and run RM.EXE
while logged onto this directory. Enter the information
required for your system.
Finding your way around the menus
---------------------------------
Use your cursor to select the menu you want. If you are
installing RoseMail for the first time, you will probably go
from start to finish, without jumping around much.
Context-sensitive help
----------------------
For each area you need to configure, an information box, or
"tickler help," pops up at the bottom of your screen. If you
are unsure how to answer a question or fill in a field,
remember to look for this help.
Tickler help is available in each screen in the RoseMail System
Manager. You can take advantage of this feature to familiarize
yourself with the configuration before you actually begin
making changes.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 66
The information box (or "tickler help") changes when you use
the arrow keys to move your cursor. You can review the
possible menu selections by moving your cursor from one submenu
to another.
THE ROSEMAIL SYSTEM MANAGER'S MAIN MENU
---------------------------------------
In the screen simulation below, please notice that the symbol
"<==" represents the location of the cursor (highlight).
When you start the RoseMail System Manager, your first screen
looks something like this.
Screen 3. The RoseMail System Manager's main menu
┌────────────────────────────────────────────────────────────────┐
│ Serial #1545. │
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ │
│ File Paths <== RoseNet Information │
│ Compression Programs Networks/NetMail │
│ Transfer Protocols Conference data │
│ Transfer rates/limits User Flags │
│ Local board information Add In Files │
│ Duplicate checking Magazines │
│ Options Conference Optimize │
│ │
│ Press ESC to exit │
│ │
│ Set locations of needed files and edit help files. │
│ │
└────────────────────────────────────────────────────────────────┘
DESCRIPTION OF SUBMENUS
-----------------------
Here is a very brief description of each item on the main menu of
the RoseMail System Manager. For more detailed information, see
the descriptions under the heading "THE ROSEMAIL SYSTEM MANAGER:
SUBMENUS", below.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 67
File Paths
----------
This is where you record the locations of the files that RoseMail
uses. You can also edit the help screens from this menu.
Compression Programs
--------------------
Here you define the compression programs you make available to
your callers, and edit the command lines for them.
Transfer Protocols
------------------
Here you list the transfer protocols you make available to your
callers. Also, from this menu, you can edit the command lines for
your transfer protocols.
Transfer rates/limits
---------------------
This area provides a table where you can specify estimated
transfer times based on the connect speed, and define the maximum
mail packet size a caller may take.
Local board information
-----------------------
Here you provide information on your BBS, as well as some other
related and unrelated information.
Duplicate checks
----------------
Here, you specify what type of duplicate checking you wish to use,
and run a program to rebuild your duplicate-checking index files
(RDX files). You also set here the number of RoseNet messages you
wish to track for duplicate checking in the RoseNet RDX file.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 68
Options
-------
Set various RoseMail options.
RoseNet Information
-------------------
Here you configure your RoseNet mail system. You specify your
RoseNet identity, that is, the name you use for your board on the
RoseNet mail system [as opposed to your mail packet name, though
these two may be the same. You specify the location of files such
as the Direct Mail (DM) directory, and log files, and select
certain RoseNet Options.
Networks/NetMail
----------------
From this menu, you set and define the list of networks you make
available to your callers. You specify which conferences belong
to which network, and define Net Sysop access to your BBS.
Conference data
---------------
Here you can set flags for each conference that control caller
access and supply certain kinds of files, such as news, bulletins,
and lists of files available for download through RoseMail.
User Flags
----------
Here, you have a list of your users, for whom you can set flags
for each conference. For net sysop access to your system,
however, you use the Net Sysop Access submenu, under the
Networks/NetMail category on the main menu. This is also where
you set access to your RoseMail Door, to your RoseNet mail system,
and to prescans of mail packets for your users.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 69
Add In Files
------------
Here you specify drives, pathnames and security level required for
access, for files you provide that can be added to a mail packet
automatically.
Magazines
---------
Here you list the locations and names of any magazines or articles
you provide for your callers through RoseMail, and you specify the
security level that allows access to these items.
Conference Optimize
-------------------
Here, when you press Enter with the menu highlighted, you create
or update the file called OPT.LST.
NOTE: RoseMail 2.00 omits the EXIT menu item that was contained
in earlier versions of RoseMail. Instead of being a submenu, the
prompt "Press ESC to EXIT" appears below the submenus. The same
principles apply as to earlier versions of RoseMail. Files such
as User files, RDX files, the new CONFDATA.DAT file and OPT.LST,
are all updated at the time you run routines from the submenus.
RoseMail's main configuration file, RMAIL.DAT, is updated at the
time you EXIT and save your configuration. If you choose not to
save your configuration at the time you EXIT, your RMAIL.DAT will
remain unchanged, unless you are upgrading your RoseMail and the
upgrade conversion program has altered files as you entered the
RoseMail System Manager. RoseMail ALWAYS tells you if it is
making changes to files during an upgrade. Regardless, it is a
good idea, before you begin to install an upgrade, to make a copy
of your RMAIL.DAT file in a separate location.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 70
THE ROSEMAIL SYSTEM MANAGER: SUBMENUS
--------------------------------------
FILE PATHS
----------
8-A) Select File Paths, and enter any necessary information,
filling in the details as illustrated below.
File Locations
--------------
Here you set locations of needed files. Detailed assistance is
provided below.
Edit help screens
-----------------
From this submenu you can edit the help screens that your
callers access while in the RoseMail Door, when they type "?"
or "H" at the RoseMail Command prompt.
Here is a simulated File Paths screen, with some information
filled in as examples. Specific instructions are included below.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 71
Screen 4. RoseMail System Manager: File Paths.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ File location and help screen editor │
│ ASCII Editor : C:\PROG\QNORT.EXE │
│ ANSI Editor : C:\PROG\THEDRAWR.EXE │
│ RMail Directory : C:\PCB\ROSE │
│ CONFDATA.DAT : C:\PCB\ROSE\CONFDATA.DAT │
│ PCBoard.DAT file: PCBOARD.DAT │
│ PCBoard.SYS file: PCBOARD.SYS │
│ USERS.SYS file : USERS.SYS │
│ Work Directory : C:\PCB\WORK# │
│ │
│ Initial screen Download help Protocol help │
│ Main menu Upload help Compression help │
│ New user screen Pointer reset help Add-In help │
│ Help on help Selection help Magazine help │
│ Press ESC (right mouse button) to return to main menu │
│ │
│ Enter the name of an ANSI editor to use to edit the ANSI help │
│ files. This entry is only used by the configuration program. │
│ │
└────────────────────────────────────────────────────────────────┘
ASCII Editor
------------
8-A-1) Enter the name of a text editor to use to edit the
ASCII help files. The program name you enter here
affects only the RoseMail System Manager. It takes
effect immediately.
Your text editor must save files in pure ASCII format;
that is, your saved file must be free of the formatting
codes that most word processors insert.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 72
ANSI Editor
-----------
8-A-2) Enter the name of an ANSI editor to use to edit the
ANSI help files. The program name you enter here
affects only the RoseMail System Manager. It takes
effect immediately.
The default help screens that callers access in the
RoseMail Door (the ones that come in your original .ZIP
file) contain PCBoard color codes, so if you want to edit
them, you will be most comfortable if you use a program
that makes such editing easy.
Editing the Help Files
----------------------
You can edit the help files from the File Paths menu by selecting
the help file you wish to edit. You can use your Down Arrow to
move your cursor into the bottom part of the menu, where the help
files are listed. This menu will scroll as necessary, to allow
you access to all the help files. Press F1 to edit the ASCII text
version of the help file. Press F2 to edit the ANSI version. You
must have specified your ASCII editor and your ANSI editor before
you can edit these files.
Rmail Directory
---------------
8-A-3) Rmail Directory: This is your RoseMail program
directory, the one where you keep your RoseMail EXE
files, your ROSEMAIL (keyword) file, your global
RoseMail configuration file (RMAIL.DAT), and your
ROSEMAIL.KEY file if you are registered. We have
called this directory C:\PCB\ROSE. If you are running
a multi-node system, all your nodes from which
RoseMail is run will access this directory.
RoseMail's .TXT (Help) files must be placed in a
subdirectory off this directory, and that subdirectory
must be called \TEXT (in this guide; it is called
C:\PCB\ROSE\TEXT). Also, RoseMail creates other
subdirectories off C:\PCB\ROSE automatically during
operation.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 73
CONFDATA.DAT
------------
8-A-4) CONFDATA.DAT (or whatever you choose to name this
file) records the flag settings you choose under the
Conference data menu, but does not include the pack
counts. CONFDATA.DAT also includes the network
translation tables for all nets. The file is shared
between all nodes, so you should put it in your
RoseMail program directory. However, you can, if you
wish, configure a node for special purposes, and
within that configuration, you may change conference
data for whatever purpose you have in mind, such as
allowing certain callers access to certain
conferences, while hiding them entirely from callers
who do not have access to that node (this latter
operation would normally involve a PCBoard operation
such as using a separate PWRD file for the node
concerned, and it will also require a separate
RMAIL.DAT file, as well as a copy of your ROSEMAIL.KEY
file, for that node). If you make a separate
CONFDATA.DAT file for a node, you should place it in
the node directory concerned, and configure your
RMAIL.DAT (or RMAIL.<node number> file for that node
accordingly.
Other File Paths
----------------
Note for single-node sysops
---------------------------
Sysops of single-node systems: In the instructions that
follow, you may treat the term "current node" as meaning "Node
1" (your only node). You can leave the locations of
PCBOARD.DAT, PCBOARD.SYS and USERS.SYS untouched. Just leave
the filenames in place as they appear by default.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 74
Note for multi-node sysops
--------------------------
Sysops of multi-node systems: If, as we recommend in this
guide, the caller is logged onto the node directory at the time
RoseMail is opened, so that the node directory is the same as
the current directory, and all your PCBOARD.DAT files are in
their respective node directories, you can leave the File Path
designations for PCBOARD.DAT, PCBOARD.SYS and USERS.SYS just as
they come by default.
If the "keyword" files for all the door programs you run return
the caller to the node directory at the time the caller exits
the door program, and if you do not change the caller out of
the node directory in the ROSEMAIL (keyword) file, the caller
will stay logged onto the current node. Then you will NOT need
to use drive or pathnames for the locations of PCBOARD.SYS nor
of USERS.SYS, since these either exist or are created in the
current directory at the time they are needed.
You will only need to provide a drive or pathname for
PCBOARD.DAT if you have some special configuration that puts
this file in some location other than its expected one, which
is the node, or the current, directory. If you move a node's
PCBOARD.DAT file, you may use a DOS environment variable in the
File Paths location for PCBOARD.DAT. You might use the PCBoard
14.5a variable PCBDAT for this purpose, since it provides the
full drive and pathname for PCBOARD.DAT. If your version of
PCBoard does not set this variable automatically, you can set
it in your BOARD.BAT for each node concerned.
If you use the variable PCBDAT, surround it with percent signs
(%) when you type it in the File Path location for PCBOARD.DAT.
You may also want to use the PCBoard 14.5a "/FILE:" switch on
the command line in your BOARD.BAT (consult the PCBoard 14.5a
manual for details).
PCBOARD.DAT
-----------
8-A-5) Enter the name and location of the PCBOARD.DAT file
for the current node. Usually, you will enter only
"PCBOARD.DAT".
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 75
PCBOARD.SYS
-----------
8-A-6) Enter the name and location of the PCBOARD.SYS file
for the current node. Usually, you will enter only
"PCBOARD.SYS".
USERS.SYS
---------
8-A-7) Enter the name and location of the USERS.SYS file for
the current node. Usually, you will enter only
"USERS.SYS".
Work Directory
--------------
8-A-8) Enter a directory name for RoseMail to use as a work
area. This directory and its entire contents will be
deleted each time a caller exits the door. Each node
must have a work directory distinct from that of any
other node. You may use "#" or "%PCBNODE%" in the
directory name, to have RoseMail substitute the node
number (in digits) for the variable (# or %PCBNODE%),
thus providing a distinctive name for each work
directory. If you are following the recommendations
in this guide, you can use the default,
"C:\PCB\WORK#", and change only the drive letter if
your PCBoard program directory resides on a drive
different from C.
Note: This is the location RoseMail uses to generate
mail packets, which is why each node must have its
own separate work directory.
If you have used the default file locations for
PCBOARD.DAT, PCBOARD.SYS and USERS.SYS, you may skip the
next section and go on to the Compression menu. If you
wish to use DOS environment variables in the File Paths,
please read on.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 76
USING DOS ENVIRONMENT VARIABLES IN FILE PATHS
---------------------------------------------
When configuring File Paths for multi-node systems, keep in mind
that we recommend you use the default configuration for File Path
specifications for the PCBOARD.DAT, PCBOARD.SYS, and USERS.SYS
files, in order to keep your configuration simple and easily
maintainable. If, however, you have a non-standard configuration,
you may use DOS environment variables in your File Paths
configuration, as follows.
PCBoard 14.5a DOS environment variables
---------------------------------------
PCBoard 14.5a provides a series of DOS environment variables,
PCBDRIVE, PCBDIR, PCBDAT and PCBNODE, automatically, unless you
disable them with PCBoard's /NOENV switch. If, for whatever
reason, the caller is not logged onto the node directory at the
time RoseMail is started, because a cd\<subdirectory> command
intervenes somewhere, you may wish to use these environment
variables in your File Paths. Consult the PCBoard 14.5a manual
(at the time of this writing, it is the WHATSNEW file) for
details.
DOS environment variables in File Paths
---------------------------------------
RoseMail versions 1.70 and up accept system (DOS) environment
variables in the configuration for File Paths.
You may use the variables that PCBoard 14.5a sets
automatically, at the time a DOOR loads, or, if you have not
upgraded to PCBoard 14.5a, or if you are using the 14.5a /NOENV
switch, you may set the variables yourself, for instance, in
your BOARD.BAT files for each node. If you set the variables
yourself, you may name them as you like, although you might use
the names mentioned just above, to reduce confusion when you
talk to other sysops or read RoseMail guides. You will at
least want to make sure the variables you use in the File Path
locations have actually been set at the time a caller starts
RoseMail on your system.
Sysops running PCBoard 14.5 (who have not upgraded to version
14.5a) may set these variables or similar ones in the BOARD.BAT
files for each node.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 77
When you have made sure that the variables will be set in the
DOS environment at the time a caller opens your RoseMail Door,
you may refer to them in your file path designations. When you
do so, remember to surround them with percent signs (%), just
as you would use a DOS environment variable in a batch file.
For a few examples of DOS environment variables in the File
Path locations, see the examples that follow.
Examples:
For the Location of PCBOARD.DAT file, enter only:
%PCBDAT%
For the Work Directory, enter:
%PCBDRIVE%%PCBDIR%\WORK%PCBNODE%
Notice in the example above that you do NOT use a backslash
between "WORK" and "%PCBNODE%", because the digits that
represent node numbers will be substituted for "%PCBNODE%",
making a directory name that includes "WORK" followed
immediately by the digits. Notice also that you do NOT
include a backslash between "%PCBDRIVE%" and "%PCBDIR%",
because the PCBoard 14.5a variable for PCBDIR begins with a
backslash. Notice also that the PCBoard 14.5a variable for
PCBOARD.DAT always includes the full drive and pathname. In
short, pay careful attention to how you enter these variables
in the File Paths configuration, and, if you are running
PCBoard 14.5 (not 14.5a), and setting the variables yourself
in your BOARD.BAT files, you will need to set them to conform
properly with your File Path configurations.
Examples of File Path configuration
-----------------------------------
Example 1
---------
Setting file paths where PCBOARD.DAT, PCBOARD.SYS and USERS.SYS
will always be found in the current directory (node directory).
This example will serve both for multi-node and for single-node
sysops.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 78
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ File location and help screen editor │
│ ASCII Editor : C:\PROG\QNORT.EXE │
│ ANSI Editor : C:\PROG\THEDRAWR.EXE │
│ RMail Directory : C:\PCB\ROSE │
│ CONFDATA.DAT : C:\PCB\ROSE\CONFDATA.DAT │
│ PCBoard.DAT file: PCBOARD.DAT │
│ PCBoard.SYS file: PCBOARD.SYS │
│ USERS.SYS file : USERS.SYS │
│ Work Directory : C:\PCB\WORK# │
│ │
└────────────────────────────────────────────────────────────────┘
If you are making a non-standard setup, it is possible to use DOS
environment variables in your File Path designations, assuming you
are using PCBoard version 14.5a, or that you set these variables
in your BOARD.BAT for each node. This second example shows how
you might use these variables.
Example 2
---------
Using environment variables in the File Paths locations for
PCBOARD.DAT, PCBOARD.SYS, USERS.SYS, and the Work Directory:
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ File location and help screen editor │
│ ASCII Editor : C:\PROG\QNORT.EXE │
│ ANSI Editor : C:\PROG\THEDRAWR.EXE │
│ RMail Directory : C:\PCB\ROSE │
│ CONFDATA.DAT : C:\PCB\ROSE\CONFDATA.DAT │
│ PCBoard.DAT file: %PCBDAT% │
│ PCBoard.SYS file: %PCBDRIVE%%PCBDIR%\PCBOARD.SYS │
│ USERS.SYS file : %PCBDRIVE%%PCBDIR%\USERS.SYS │
│ Work Directory : C:\PCB\WORK# │
│ │
└────────────────────────────────────────────────────────────────┘
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 79
NOTES
(1) Make certain that your configuration for the Work
Directory assigns a DIFFERENT directory for each node.
The Work Directory is deleted after each use.
(2) You can use either "#" or "%PCBNODE%" in the location
of the Work Directory to have RoseMail substitute the node
number (in digits) for "#" or for "%PCBNODE%".
Example 3
---------
Setting your own environment variables for use in File Path
configuration (if you are running PCBoard 14.5, and have not
upgraded to version 14.5a). Note that the variables in this
example are set for node 2. You will need to set them
appropriately in each BOARD.BAT.
Example BOARD.BAT for NODE 2
----------------------------
@ECHO OFF
C:
CD \PCB\NODE2
SET PCB=/MAIN /SWAP
SET PCBDRIVE=C:
SET PCBDIR=\PCB\NODE2
SET PCBDAT=C:\PCB\NODE2\PCBOARD.DAT
SET PCBNODE=2
SET DSZPORT=2F8,3
SET DSZLOG=PCBDSZ.LOG
IF EXIST REMOTE.BAT RENAME REMOTE.BAT REMOTE.SYS
IF EXIST EVENT.BAT RENAME EVENT.BAT EVENT.SYS
IF EXIST DOOR.BAT DEL DOOR.BAT
IF EXIST ENDPCB DEL ENDPCB
PCB145
IF EXIST REMOTE.BAT REMOTE
IF EXIST DOOR.BAT DOOR
IF EXIST EVENT.BAT EVENT
IF EXIST ENDPCB GOTO END
BOARD
:END
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 80
The #-variable in File Paths
----------------------------
In some previous versions of RoseMail (1.61 or 1.60 or below),
you may have used the "#-variable" in the File Path location
for PCBOARD.SYS. If you did this, and you plan to keep your
old configuration, and you retain multiple ROSEMAIL (keyword)
files, one for each node directory, you will need to use what
we call "the /n switch" on the command line for each ROSEMAIL
file. See the description of the /n switch below if you need
assistance.
RoseMail versions 1.70 and up no longer need the "#-variable"
to designate a node number in the File Paths configuration. If
you do use a variable for which the digits of a node number
will be substituted, you can either use the DOS environment
variables provided automatically by PCBoard 14.5a, or, if you
are running PCBoard 14.5, you can set DOS environment variables
yourself in the BOARD.BAT for each node. You may, however,
wish to use "#" in the File Path location for the Work
Directory, to save yourself typing the longer "%PCBNODE%",
since "#" will have the same effect as "%PCBNODE%" in these
circumstances.
In case you are already set up using the "#-variable," and do
not wish to change your configuration, here is a description of
how the "#-variable" works.
You can use the symbol "#" as a variable when entering file
locations in the File Paths configuration area of the RoseMail
System Manager. We call this the "#-variable". For the "#"
symbol in the File Path locations, RoseMail will substitute the
node number a caller has logged onto. Therefore, you may use
this symbol in the directory names in the File Paths
configuration to represent the digits that designate node
numbers.
When you use "#" in a file path designation, the symbol "#"
will be replaced with the digits that represent the node
number. "##" will be padded to two characters. "###" will be
padded to three characters. For instance, "##" would
substitute "09" for Node 9, and "###" would substitute "009"
for Node 9.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 81
The #-variable and the PCBNODE variable
---------------------------------------
If you are running PCBoard 14.5, and have not upgraded to version
14.5a, you can use "#" to designate file paths. RoseMail will
translate the symbol "#" or "##" or "###" (without the quotes)
into the digits of the node number called, at the time a caller
opens the RoseMail Door. The following table illustrates the use
of the #-variable:
Table 2. The #-variable and its substitutions in File Paths.
┌────────────────────────────────────────────────────────────────┐
│ Use - to get these numbers - with these results │
│ -------------------------------------------------------------- │
│ │
│ # - numbers with no leading zeros - 1 - 9 - 99 - 999 │
│ ## - numbers with zeros on 1 to 9 - 01 - 09 - 99 - 999 │
│ ### - numbers with zeros on 1 to 99 - 001 - 009 - 099 - 999 │
│ │
└────────────────────────────────────────────────────────────────┘
For instance, let us say that in the File Paths configuration, you
point to PCBOARD.SYS by specifying
C:\PCB\NODE#\PCBOARD.SYS
or, for PCBoard version 14.5a:
%PCBDRIVE%%PCBDIR%\NODE%PCBNODE%\PCBOARD.SYS
Then, when a caller calls on Node 2, the File Path for PCBOARD.SYS
will become C:\PCB\NODE2. When a caller calls on Node 5, the File
Path will become C:\PCB\NODE5. When a caller calls on Node 14,
the File Path will become C:\PCB\NODE14.
If you use the #-variable or the DOS environment variables new
with PCBoard 14.5a to point to PCBOARD.SYS, you will also need to
add the /n switch to the command line in the ROSEMAIL (DOOR) file,
as described in the section "Adding the /n switch", just below.
More detail is given under "action" paragraph 9 near the end of
the main reference section, which describes how to configure
individual nodes in special ways.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 82
We recommend that if you are running multiple nodes, you do use
either "#" or "%PCBNODE%" in the File Path for the Work Directory.
If you use "#" or "%PCBNODE%" to point to the Work Directory, you
will NOT need to add the /n switch to the command line in the
ROSEMAIL (keyword) file, nor will you need to make multiple copies
of the ROSEMAIL file and place one in each node directory. Using
"#" or "%PCBNODE%" in the location of the Work Directory merely
ensures that each node will have its own Work Directory. It is
only when you use the #-variable in the File Path location for
PCBOARD.SYS that you must use the /n-switch on the ROMAIL command
line in your ROSEMAIL (keyword) file. The only purpose for such a
maneuver would be to configure a node for special purposes.
Adding the /n switch
--------------------
If you use the #-variable or a variable such as PCBNODE in the
File Paths location for the file PCBOARD.SYS, which we assume
you will only do if you are configuring a node for special
purposes, so that you cannot use the shared (or global)
configuration for this particular node, you will need to add a
switch to represent the node number to the end of the node-
specific ROMAIL command line in your ROSEMAIL (keyword) file,
to ensure that ROMAIL locates the correct node.
To do this, edit the ROMAIL command line that applies to this
particular node, and add to its very end a space, and then
"/nn", where "nn" represents the actual digits for the node
number.
For example, if you are configuring Node 3 for a special
purpose, AND if you have used "#" in the File Path location for
PCBOARD.SYS, then you should edit your ROSEMAIL file, and add
"/3" to the ROMAIL command line, ONLY in the branch for Node 3,
something like this:
C:\PCB\ROSE\ROMAIL RMAIL.3 /3
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 83
Notice in the example that the RMAIL.DAT file specific to Node
3 has also been identified on the command line, so that it
precedes the /n-switch. In other words, a branch to a specific
node in the ROSEMAIL (keyword) file will usually contain at
least one argument on the command line, and that will be the
name of the RMAIL.DAT file to be used, whether it retains the
standard name "RMAIL.DAT", or whether it has been renamed to
"RMAIL.<node_number>". The /n-switch argument will follow the
RMAIL.DAT argument, and spaces will separate the arguments from
the command "ROMAIL" and from each other.
Summary of "#" or "%PCBNODE%" recommendations
---------------------------------------------
Summary: The simplest configurations do NOT require you to use
these variables, even on a multi-node system, except in the
location of the Work Directory, so we recommend that you use them
in other File Path locations only if your system structure and
strategy force you to use them.
If you are running a single-node system, we recommend that you do
not use these variables except in the location of the Work
Directory.
If you are running a multi-node system, and you have the same
configuration for all nodes, we recommend that you omit the
#-variable and the DOS environment variables provided by PCBoard
14.5a from all File Path specifications except for that of the
Work Directory.
If you are configuring one or more nodes, individually, in special
ways, we recommend that you add special branches to your global
ROSEMAIL (keyword) file to accommodate these special
configurations. These branches are described near the end of the
main reference section, under paragraph 9.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 84
COMPRESSION PROGRAMS
--------------------
8-B) Define the compression programs you will use with
RoseMail.
Here you list the types of compression programs you make available
to the user. Two commonly used archiving programs have been
predefined. You can add any others that you and your users agree
on.
You may also delete from this screen listings of archivers that
you do not use.
The pre-defined compressors include PKARC and PKZIP. Information
is listed in several columns, with the rightmost area initially
off-screen to the right.
To change your view from the leftmost side to the rightmost, use
your TAB key, and to reverse directions, use Shift-TAB.
Remember that you can use Ctrl-Y to delete the information in a
field, and, if you have not moved the cursor off the field, you
can use Ctrl-U to restore the information that was present when
you began your current session.
When you enter information here, keep in mind that each program's
ID (the first HEX code in the file) must be recorded here, so that
RoseMail can identify the type of compression used in the file.
(Remember that the ID is expressed in HEX, not decimal, notation.)
Remember too that the command line options you want must be
included here, since the programs are run from these command lines
(which are saved in RMAIL.DAT). You may, of course, edit the
switch designations, changing those shown here. For instance, in
the PKZIP program, you could change "PKZIP -ES" (shrink) to "PKZIP
-EX" (implode).
You could also add another definition for PKZIP, and have one with
the "-ES" switch and one with the "-EX" switch, thus giving your
callers a choice of compression methods using the same program.
In the simulated screen below, note the "==>" Here, this symbol
actually shows on your RoseMail System Manager screen. It
indicates that you press TAB to scroll the screen to see new
information.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 85
Screen 5. Compression Program.
┌────────────────────────────────────────────────────────────────┐
│ │
│ Letter ID Name Compression program ==> │
│ A 1A Phil Katz's PKARC PKARC -a │
│ Z 50 Phil Katz's PKZIP PKZIP -ES │
│ │
└────────────────────────────────────────────────────────────────┘
The column headings shown above mean:
Letter
------
This letter is the letter the caller presses to select the
compression program from the RoseMail Door.
ID
--
In the ID column, you see the first character (in hex) of the
compressed file. RoseMail uses this character to identify what
type of compression was used for an uploaded mail packet. (50
[HEX] for ZIP, 1A for ARC, FF for LHA, 60 for ARJ).
Name
----
In the next column, place the Compressor's program name. The name
merely describes the program for the caller; it is not a command.
Compression program (executable filename)
-----------------------------------------
Here, you enter the filename of the program to execute; that is,
you type the actual command to compress. In other words, this
line works in the same way as the DOS command line.
Therefore, you need to include any switches here that you would
type on a DOS command line.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 86
You may TAB to the rightmost part of the screen. Once more, the
"<==" symbol here actually shows on your screen. It means you can
press Shift-TAB to scroll the screen.
Screen 6. Decompression program.
┌────────────────────────────────────────────────────────────────┐
│ │
│ Letter ID Name Decompression program <== │
│ A 1A Phil Katz's PKARC PKXARC -r │
│ Z 50 Phil Katz's PKZIP PKUNZIP -O │
│ │
└────────────────────────────────────────────────────────────────┘
Decompression program (executable filename)
-------------------------------------------
Here, you enter the filename of the program to execute; that is,
you type the actual command to decompress. In other words, this
line works in the same way as the DOS command line.
Therefore, you need to include any switches here that you would
type on a DOS command line.
RoseMail should work well with the default settings, so if you are
using only PKARC or PKZIP, you may leave everything as it is, and
go on to the next step (Transfer Protocols).
8-B-1) If you are going to change or add anything to the
compression definitions, you may do so now.
Adding extra configurations for the same compression program
------------------------------------------------------------
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 87
You may add more configurations for the same compression program.
Make sure you use a different selection letter (or even a digit).
Fill out the other fields appropriately, and check to make sure
that the executable program names are specified correctly. With
the appearance of PKZ204E.EXE (using PKZ204C.EXE is not
recommended, since it caused difficulties on some systems), you
may wish to enter additional lines making it a choice for your
callers. If you add other versions of the same program, the ID
Byte will probably be the same for both. PKZIP, for instance,
uses the (HEX) ID byte of "50" for versions 1.10 and 2.04. You
could name your programs PKZIP1.EXE and PKUNZIP1.EXE, and
PKZIP2.EXE and PKUNZIP2.EXE to distinguish the two versions. Just
make sure that all these versions are named correctly, and that
they are in your DOS search path. You could make your screen look
somthing like the following illustration.
Screen ##: Compression: different versions of the same program
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Packet compression information │
│ │
│ Letter ID Name Compression program ==> │
│ Z 50 Old PKZIP,Slow-Small Size PKZIP1.EXE -ex │
│ X 50 Old PKZIP,Fast-Large Size PKZIP1.EXE -es │
│ 2 50 PKZ204c,Slow-Small Size PKZIP2.EXE -ex │
│ 3 50 PKZ204c,Fast-Large Size PKZIP2.EXE -es │
│ │
└────────────────────────────────────────────────────────────────┘
You can see that the ID byte is the same for all of these
selections, but that the command lines are different.
If you are running both version 1.10 and 2.04 of PKZIP, you may
wish to use the downward-compatible version of PKUNZIP for all
selections. To do this, you would simply repeat the same command
line under Decompression programs for each of your PKZIP
selections, whether for version 1.10 or 2.04, as illustrated
below.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 88
Screen ##: Using PKUNZIP version 2 for all unZIPping
┌────────────────────────────────────────────────────────────────┐
│ │
│ Letter ID Name Decompression program <== │
│ Z 1A PKZIP 1.10, Slow PKUNZIP2 -O │
│ X 50 PKZIP 1.10, Fast PKUNZIP2 -O │
│ 2 50 PKZIP 2.04, Slow PKUNZIP2 -O │
│ 3 50 PKZIP 2.04, Fast PKUNZIP2 -O │
│ │
└────────────────────────────────────────────────────────────────┘
TRANSFER PROTOCOLS
------------------
General Information
-------------------
RoseMail 2.00 comes with a set of internal protocols, although it
is set up by default to use DSZ.COM. See the descriptions below
for more detail.
Previous versions of RoseMail had no internal protocols; you, the
sysop, provided them. Since DSZ is almost universally used with
PCBoard, presumably you have that program available. If you do
not have DSZ, most PCBoard BBSs carry it, under the filename
DSZnnnn.ZIP, where "nnnn" is a four-digit number representing the
date of release.
You will need the registered version of DSZ to achieve its full
and proper operation with RoseMail.
Examples are also given of the command lines for HS/Link, which
you can use either for its full capability as a bi-directional
protocol, or for single-direction transfers.
The screen for Transfer Protocols contains several fields that
identify and define the protocols. These are followed by two sets
of command lines, one for SENDing files to the caller (these are
for caller downloads), and one for RECEIVing files from the caller
(these are for caller uploads).
The five most commonly used communications protocols used from DSZ
have been predefined (Xmodem, Ymodem, Zmodem, Ymodem-G, and
Zmodem-MobyTurbo). You can add to this list as your needs dictate.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 89
Remember that RoseMail stores the command lines for the protocols
you define in its configuration file, RMAIL.DAT, instead of using
external batch files. The command lines illustrated in this guide
are for DSZ. They are the default command lines that come with
your original ZIP files.
Because RMAIL.DAT holds the command lines for all protocols you
use with RoseMail, you configure those commands from this menu.
The defaults for DSZ that come with RoseMail will work on some BBS
systems just as they are.
A reminder: if you have not set a path to DSZ using the DOS
path command, and are not planning to do so, you will need to
point to its location by editing the command lines from this
menu. Instructions for doing so are included in the
appropriate place below.
If you wish to install protocols other than those provided by DSZ,
please consult the documentation for those protocols. Enter the
information for other protocols in the same way as you would for
DSZ.
Orientation to the Transfer Protocol screens
--------------------------------------------
When you configure transfer protocols, you will see the leftmost
information first. This includes information that identifies the
protocols and defines some of their characteristics, and it shows
the command lines for the Download program (caller RECEIVE, you
SEND).
The "==>" symbol in the screen below indicates that you can press
TAB to scroll the screen.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 90
The initial screen looks something like this:
Screen 7. Transfer protocol information
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Transfer protocol information │
│ │
│Let Err Bat Name Download program ==> │
│ X N N XModem DSZ.COM speed %1 port %2 sx │
│ Y N Y YModem DSZ.COM speed %1 port %2 sb -k │
│ Z N Y ZModem DSZ.COM speed %1 port %2 sz │
│ G Y Y YModem-g DSZ.COM speed %1 port %2 sb -g -k │
│ M N Y ZModem-MobyTurbo DSZ.COM speed %1 port %2 sz -m │
│ O N N Xmodem-1K DSZ.COM speed %1 port %2 sx -k │
│ │
│ Press F2 to select internal protocols │
│ Press ESC (right mouse button) to return to main menu │
│ │
│ Protocol selection letter. This letter is the letter that the │
│ user presses to select the protocol. │
│ │
└────────────────────────────────────────────────────────────────┘
The column headings mean:
Let
---
This is the protocol selection letter - that is, it is the letter
that the user presses to select the protocol.
Err
---
This column shows which protocols require an error-correcting
connection for their use. If a protocol you install here requires
an error correcting connection, set this flag to Y.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 91
Bat
---
This column shows which protocols permit batch uploads and
downloads. Note well: this column has nothing to do with batch
files. We are talking about file transfers here, done in batches.
If a protocol you install permits batch uploads/downloads, set
this flag to Y. If it does not, set it to N.
Name
----
This is the name of the protocol. This is only used as a
description to the user; it does not provide the executable
function. (The executable files are called in the command line
areas, under "Download program" and "Upload program.")
Download program
----------------
This is the name of the program to perform downloads, including
all command line options required. Use %1 to insert DTE speed
(that is your computer-to-modem speed), %2 for com port in use, %3
for filename, %4 for connect speed, and %5 with bi-directional
protocols to specify upload location. Remember that this is a
download for the user so you should be using commands to send the
file.
When you TAB to the right, you see a second list of command lines;
these are for the Upload (caller-upload; your download) program.
They are the command lines that allow you to RECEIVE files.
The symbol "<=>" in the simulated screen below indicates that you
can press TAB to scroll the screen one way, and Shift-TAB to
scroll in the other direction.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 92
Screen 8. Transfer Protocols: DSZ Command Lines.
┌────────────────────────────────────────────────────────────────┐
│ │
│ Let Err Bat Name Upload program <=> │
│ X N N XModem DSZ.COM speed %1 port %2 rx %3 │
│ Y N Y YModem DSZ.COM speed %1 port %2 rb -k │
│ Z N Y ZModem DSZ.COM speed %1 port %2 rz │
│ G Y Y YModem-g DSZ.COM speed %1 port %2 rb -g -k │
│ M N Y ZModem-MobyTurbo DSZ.COM speed %1 port %2 rz -m │
│ │
└────────────────────────────────────────────────────────────────┘
Upload program
--------------
This is the name of the program to perform uploads, including all
command line options required. Use %1 to insert DTE speed (that
is your computer-to-modem speed), %2 for com port in use, %3 for
filename, %4 for connect speed. You do not use %5 (upload
location for bi-directional protocols) with the upload program,
because your system is already configured to receive files in
specified places. Remember that this is an upload for the user so
you should be using the commands to receive the file.
The symbol "<==" in the simulated screen below shows that you can
press Shift-TAB to scroll the screen.
When you TAB once more, the rightmost portion of this area
appears. It looks something like this:
Screen 9. Transfer Protocols: Environment Variable.
┌────────────────────────────────────────────────────────────────┐
│ │
│ Let Err Bat Name Environment variable <== │
│ X N N XModem DSZLOG │
│ Y N Y YModem DSZLOG │
│ Z N Y ZModem DSZLOG │
│ G Y Y YModem-g DSZLOG │
│ M N Y ZModem-MobyTurbo DSZLOG │
│ │
└────────────────────────────────────────────────────────────────┘
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 93
Environment variable (DSZLOG)
-----------------------------
This is the name of the variable in the DOS environment (created
with the DOS SET command) that the transfer program reads to
determine where the log files should be written. Only DSZ-
compatible logs are supported. If the protocol cannot create DSZ-
compatible logs or cannot return error levels correctly, leave
this field blank.
NOTE: You never get to see the DSZ.LOG file; RoseMail uses it,
but deletes it when the transfer is complete.
INTERNAL PROTOCOLS
------------------
As mentioned above, RoseMail 2.00 comes with internal protocols to
provide compatibility with PCBoard /M. You can select any or all
of these by pressing F2 from the Transfer Protocols screen. You
may substitute any of them for external protocols, or add them as
additional choices for your callers. If you add them, you will
have to provide different selection letters from those you already
have in place. You may use the letters of the alphabet, and also,
single digits, as selection "letters" in this area.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 94
Screen ##: Selecting RoseMail's internal protocols
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Transfer protocol information │
│ │
│Let Err Bat Name Download program ==> │
│ X N N XModem C:\PCB\DSZ.EXE speed %1 port │
│ Y N Y YModem ┌────────────────┐.EXE speed %1 port │
│ Z N Y ZModem │XModem-Checksum │.EXE speed %1 port │
│ G Y Y YModem-g │XModem-CRC │.EXE speed %1 port │
│ M N Y ZModem - MobyTu│XModem-1K │.EXE speed %1 port │
│ O N N Xmodem-1K │XModem-1K-G │.EXE speed %1 port │
│ N N │YModem │ │
│ N N │YModem-G │ │
│ N N │ZModem │ │
│ N N └────────────────┘ │
│ Press F2 to select internal protocols │
│ Press ESC (right mouse button) to return to main menu │
│ │
└────────────────────────────────────────────────────────────────┘
The internal protocols available are:
- XModem protocol. Checksum error control with 128 byte
packets.
- XModem protocol. CRC error control with 128 byte packets.
- XModem-1K protocol. CRC error control with 1024 byte
packets.
- XModem-G protocol. CRC error detection with 1024 byte
packets. Packets are sent in full flow mode. It is strongly
advisable to use an error correcting modem with this
protocol.
- YModem protocol (true Ymodem). CRC error control with 1024
byte packets and batch file transfers.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 95
- YModem-G protocol. CRC error detection with 1024 byte
packets and batch file transfers. Packets are send in full
flow mode. It is strongly advisable to use an error
correcting modem with this protocol.
- ZModem protocol. CRC error control and batch file transfers.
Under "Environment variable" for the internal protocols, you
should specify DSZLOG on each line, since all these protocols are
compatible with that logging system.
CHECKLIST FOR CONFIGURING EXTERNAL TRANSFER PROTOCOLS
-----------------------------------------------------
(1) Make sure the protocol program you define is in your DOS
search path.
(2) Make sure all fields under Transfer Protocols are filled out
correctly.
(3) Make sure the Download Program and Upload Program command
lines are filled out correctly.
Note: This entire section refers to DSZ, but the principles
given here apply to all protocols. If you are installing a
different protocol, substitute the name of that protocol where
it applies.
Define Transfer Protocols
-------------------------
8-C) Define the transfer protocols you make available to the
user.
The instructions that follow are for DSZ. You may define any
other protocol you wish to.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 96
Tell RoseMail how to find DSZ
-----------------------------
If you have not told RoseMail where to find DSZ, you will need
to do that, either by setting a DOS path to its drive and
directory location in a batch file such as AUTOEXEC.BAT (see
the remarks above, under the heading "PROTOCOLS: Make sure
RoseMail will be able to find DSZ"), or by adding its location
to the command lines here in the Transfer Protocols
configuration. If you have chosen the latter method,
instructions for doing this follow below.
Configure the DSZ command lines (optional)
------------------------------------------
If you need to alter the command lines to suit your system,
some suggestions are given below. On many systems, the command
lines will function without alteration.
The section that follows describes how to point to DSZ using
RoseMail's Transfer Protocol command lines. If DSZ is in your
DOS path, you may skip this section and go on to "Check the DSZ
command lines."
This ends the checklist for what you will need to do to make sure
your Transfer Protocols are defined. We will now look at the
details of defining them.
Point to DSZ using the Transfer Protocol command lines
------------------------------------------------------
If DSZ is in your DOS path, you may skip this step.
8-C-1) Cursor to the first Download program command line,
press Right Arrow and then Left Arrow, to avoid wiping
out the line that is already present, press the Insert
key to turn Insert mode on, and then type the drive
and path name where DSZ.COM (or DSZ.EXE) is located.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 97
For example, if your default command line for Xmodem
SEND was:
DSZ.COM speed %1 port %2 sx
and DSZ is located in C:\PCB, edit it to read:
C:\PCB\DSZ.COM speed %1 port %2 sx
isk s) Repeat the previous step for each of the command lines
in the Download program area, and then Press TAB to
reach the Upload Program area, and edit each command
line here just as you did for the Download Program
area.
Note: If you forget to move the cursor EACH TIME you
change from one command line to the next, you may
experience frustration by having the default contents of
the field disappear suddenly when you begin to type.
Also, if you intend to insert text rather than type over
what is already there, and you forget to turn Insert Mode
ON, EACH TIME you move from one command line to the next,
you will be similarly frustrated. If you lose text you
wanted to preserve, simply press Ctrl-U before you move
the cursor out of the field, to restore the previous
contents.
Check the DSZ command lines
---------------------------
If you are using DSZ, a quick check that the command lines suit
you, and that DSZ is in your path, or that it is pointed to by
the command lines here, will probably suffice.
If you wish to alter the command lines, this is a convenient
time to do it.
Edit the DSZ command lines
--------------------------
If you are using DSZ.EXE instead of DSZ.COM, change the ".COM"
portion of the command lines to ".EXE"; or, instead, you may
simply delete the extension, (".COM") if you prefer.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 98
Other alterations you may make to command lines
-----------------------------------------------
The command lines provided should work with most systems.
However, if you are comfortable writing DSZ command lines, and
prefer to alter these, you may:
- delete the ".COM"
- delete the "speed %1" (But test this on your system to
make sure it works correctly, in case you have to
restore it later).
- delete the "port %2" under the following conditions:
Either your modem is on COM 1 (DSZ's default), or you
set the DSZPORT variable previously, in AUTOEXEC.BAT
or in BOARD.BAT.
If you wish to insert handshake commands, such as
"handshake both," "handshake slow," "handshake on," or
"handshake cts," you can squeeze them in by deleting
portions of the command line you do not need, and
shortening the handshake commands to their abbreviated
forms; for instance:
- handshake slow = ha slow
- handshake both = ha bo
- handshake on = ha on (This is the DSZ default.)
- handshake cts = ha cts
You may insert commands to estimate the time of transfer,
for instance:
est 0 %4
This command goes right before the command to send or
receive, (for instance, before "sx" or "rz").
IMPORTANT! If you edit the command lines, please remember
that DSZ's command lines are CASE-SENSITIVE! For further
information, please refer to the DSZ documentation.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 99
Installing other protocol programs
----------------------------------
If you add other protocols, define them here. Make sure you
fill in the necessary fields, and check that your command lines
are correct for the protocol you are installing.
Examples of command lines for other protocols
---------------------------------------------
Xmodem-1K from DSZ
------------------
Download program settings:
O N Y Xmodem-1K C:\PCB\DSZ est 0 %4 sx -k
Upload program settings:
O N Y Xmodem-1K C:\PCB\DSZ est 0 %4 rx -k %3
HS/Link by Samuel Smith
-----------------------
Download program settings:
H N N HSLINK -B%1 -P%2 -U%5
The "%5" in this line represents the location of your
upload directory. You should be sure to include the
"%5" in your command line for the caller's download, so
that the caller's simultaneous upload will find your
upload directory.
RoseMail will notice the simultaneous upload and insert
the uploaded file.
Upload program settings:
H N N HSLINK -b%1 -P%2 -U%3
HS/Link produces DSZ-compatible logs, so you should set the
Environment Variable column to "DSZLOG" for HS/Link.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 100
TRANSFER RATES/LIMITS
---------------------
In this area, you indicate the maximum packet size you wish
callers to be able to take, depending on their connect speeds,
and you show estimated transfer times for those speeds.
The following "screen" is really an amalgamation of the two
screens that show the Transfer Rate and Packet Limit Information.
Use your Down and Up Arrows to scroll the screen as needed. PgDn
and PgUp do not work on this screen.
Screen 10. Transfer Rate and Packet Limit Information.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Transfer rate and packet limit information │
│ │
│ Baud Transfer Rate Max msgs/conf Max msgs/packet │
│ │
│ 300 0 0 0 │
│ 1200 120 100 200 │
│ 2400 240 200 600 │
│ 4800 480 200 800 │
│ 7200 720 200 1000 │
│ 9600 960 200 1000 │
│ 12000 1200 200 1000 │
│ 14400 1440 200 1000 │
│ 16800 1680 200 1000 │
│ 19200 1920 200 1000 │
│ 38400 3840 200 1000 │
│ 57600 0 0 0 │
│ LOCAL 9999 300 1000 │
│ NETWORK 9999 300 1500 │
│ │
│ Press ESC (right mouse button) to return to main menu │
├────────────────────────────────────────────────────────────────┤
│ The average number of characters that can be transmitted per │
│ second at the designated connect rate. │
│ │
└────────────────────────────────────────────────────────────────┘
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 101
The consideration in filling out this area is the size of the
mail packet your callers can take in a single download (mail
scan). Callers who enable the Repeat Download feature can
download mail packets until they run out of their PCBoard time
allotments.
Here is what the column headings mean:
Transfer Rate
-------------
This is the average number of characters that can be transmitted
per second at the designated connect rate.
Max msgs/conf
-------------
The maximum number of messages that can be contained in a single
conference in the caller's mail packet at the corresponding
connect rate.
Max msgs/packet
---------------
The maximum number of messages that can be contained in the
caller's total mail packet at the corresponding connect rate.
Setting a limit on number of messages per conference
----------------------------------------------------
For each rate listed on the screen, you may set limits on how many
messages your callers may take in a single conference. For
callers whose systems have ample disk space and memory, the main
consideration here is how many messages the offline mail readers
they are using will cope with. Some reader programs are unable to
read more than 200 messages in a single conference.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 102
Setting a limit on number of messages per .QWK packet
-----------------------------------------------------
For each rate, you may set a limit on how many messages your
callers may take in a single .QWK packet. Considerations here
include the offline mail reader programs your callers use, which
may themselves have limits. Other considerations include
limitations of disk space and memory, and the amount of time it
takes a caller to download a single .QWK packet.
Caller's SIZ command
--------------------
Note that callers may set limits within those you set here for the
maximum number of messages per conference, and for the maximum
number of messages per packet. They can use the RoseMail SIZ
command to do this. See "The Caller's Guide to RoseMail" for more
information on the SIZ command.
Caller may set limit on expanded packet size
--------------------------------------------
Callers have one setting more when calling in (using
ROMAIL.EXE) than you have in the RoseMail System Manager
(RM.EXE) under Transfer Rates/Limits. This is the setting for
the maximum expanded size of the mail packet in Kilobytes. If
you are a net sysop calling RoseMail for your HUB.QWK packets,
you may wish to take advantage of this setting, which you will
find under the SIZ command in the RoseMail Door. Instructions
for making this choice are given in the Caller's Guide to
RoseMail, which is included with this documentation package.
See also the RoseMail Options submenu, where you can set the
maximum size in Kilobytes for the work area where a caller's mail
packet is put together.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 103
Caller Repeat Downloads
-----------------------
If callers cannot get all the new mail in a single mail packet
within the limits you or they set, they can get around this by
selecting Option 16 (Repeat downloading) in the RoseMail Door.
This way, they may remain in the RoseMail Door until they have
picked up all their new mail, as long as they do not exceed their
allotted BBS times.
RoseMail numbers the packets it delivers sequentially, thus:
BBS.QWK, BBS.QW0, BBS.QW1, and so on, up through BBS.Q99, which
gives a limit of 101 packets in a single session in RoseMail.
A caller who exits RoseMail but remains logged on to PCBoard may
then re-enter RoseMail and download another batch of new mail,
providing the time allotted for that session allows for this
activity. Exiting RoseMail, however, will cause the packet names
to be reset to BBS.QWK, so a caller who exits RoseMail and then
re-enters it in the same session should shell from the
communications program and rename any packets just downloaded, so
that they will not be written over or appended to.
Combining control of packet size with Repeat Downloading provides
you and your callers with maximum flexibility in handling mail
packet size and time spent online downloading mail.
LOCAL BOARD INFORMATION
-----------------------
Board Information
-----------------
This area includes information on your bulletin board, including
its name, your sysop name, your BBS phone number, and your message
packet name. It also includes a number of other configurable
items, as described below.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 104
The following screen is from the unregistered version of RoseMail.
When you register your RoseMail and download your ROSEMAIL.KEY
file, the board name, sysop name, and board telephone are
installed for you. Changes to these fields may be made by calling
the Rose Media BBS at (416) 733-2285, joining Conference 1, and
leaving a (C)omment to the sysop containing any information
required to make the changes.
Screen 11. Local Board Information.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Local board information │
│ │
│ Board name : Marigold PCBoard BBS │
│ SysOp name : Julia Kayaust │
│ Board telephone : 604-665-1212 │
│ Packet name : MARIGOLD │
│ Local directory : C:\PCB\MAIL\ │
│ Prescan dir : C:\PCB\NETOFFLN\ │
│ Network QWK dir : C:\PCB\QWKS\ │
│ Network REP dir : C:\PCB\REPS\ │
│ Trashcan file : C:\PCB\ROSE\RMTCAN │
│ │
│ Press ESC (right mouse button) to return to main menu │
│ │
│ The name that is used for the mail packets (excluding the │
│ .REP, .QWK and all other extentions). │
│ │
└────────────────────────────────────────────────────────────────┘
Board name
----------
This is the name of your bulletin board system. This information
will be recorded in the CONTROL.DAT files generated from RoseMail.
When you register, your ROSEMAIL.KEY file provides this
information.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 105
Sysop name
----------
This is the name of the sysop that you want included in the
CONTROL.DAT file.
When you register, your ROSEMAIL.KEY file provides this
information.
Board telephone
---------------
This is the telephone number for your bulletin board (main node).
When you register, your ROSEMAIL.KEY file provides this
information.
Packet name
-----------
This is the name that is used for the mail packets (do not list
any extensions, such as ".REP" or ".QWK," since these are added
automatically as needed).
Local directory
---------------
This is the directory from which you send (upload), and into which
you receive (download), mail packets during a local connection.
Prescan dir
-----------
This is the directory in which prescanned mail packets will be
placed when you use the "ROMAIL /P" command. In earlier versions
of RoseMail, this directory was called the "Offline Net Dir".
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 106
Network QWK dir
---------------
This is the directory you use for the .QWK packets that you
download from another board. This is only used if you are
inserting network mail.
Network REP dir
---------------
This is the directory where RM.EXE will place .REP packets to
upload to another board on the network. This is only used if you
are scanning for outgoing network mail.
Trashcan file
-------------
Here you enter the file name for your RoseMail trashcan file.
You use the RoseMail trashcan file to list names of callers you
wish to prevent posting and receiving messages through your
RoseMail Door.
That is, for any name you enter in the RoseMail trashcan file, you
can prevent any messages TO or FROM that name from being inserted,
or you can prevent BOTH kinds of insertions (both TO and FROM).
This lockout applies to messages uploaded into your RoseMail door
in a BBS.REP or in a HUB.REP packet, and to messages inserted by
RM.EXE from a HUB.QWK packet.
When you have the Trashcan field selected, you can press F2 to
edit your trashcan file. If you want to disable checking, leave
the filename blank.
To edit the Trashcan file, select the Local Board Information
submenu. From this submenu, select "Trashcan file". A window
will pop up that allows you to edit the name of the person you
wish to block. You can block messages sent TO the user, messages
FROM the user, or BOTH. Users who are thus "TCanned" are blocked
both from uploading QWKs into your RoseMail Door, and from
receiving messages in REP files from your RoseMail Door.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 107
Screen ##: Edit the Trashcan file
┌────────────────────────────────────────────────────────────────┐
│ │
│ Trashcan file : C:\PCB\ROSE\RMTCAN │
│ │
│ The file name for your trashcan file. No messages TO/FROM │
│ users in this list can be inserted with a RoseMail upload or │
│ RM insert. Press F2 to edit list. Leave blank to disable │
│ checking. │
│ │
└────────────────────────────────────────────────────────────────┘
When you press F2, a screen which may or may not resemble the
following appears.
Screen ##: Edit the trashcan file
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Edit the trashcan file │
│ │
│ CROOKED PERSON BOTH │
│ │
│ │
│ Press ESC (right mouse button) to return to board info menu │
│ │
│ Press 'A' to ADD a user to the trashcan. No messages TO │
│ and/or FROM a user in the trashcan will be allowed. Press 'D' │
│ to drop a user from the list. │
│ │
└────────────────────────────────────────────────────────────────┘
DUPLICATE CHECKING
------------------
RoseMail provides two types of checking to prevent entry of
duplicate messages into your message bases. One method allows
ROMAIL.EXE to check for duplicates at the time callers upload
their BBS.REP or HUB.REP files into your RoseMail Door, and the
other allows RM.EXE to check for duplicates at the time it inserts
messages from any HUB.QWK files you download.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 108
"RDX" stands for "RoseMail Dupe indeX" files. If you set either
of the duplicate checking options to "Y", the respective .EXE file
will create the .RDX files automatically. You will, however, need
to keep the .RDX files reasonably current, in order to keep up
system performance. You can rebuild the files from the DOS
command line, as described below, or you can do so from the
Duplicate checking submenu in the RoseMail System Manager.
If you set either or both of the duplicate checking options to
"Y", it is recommended that you rebuild the .RDX files weekly, to
eliminate entries for messages that have been packed out, and to
shrink the .RDX files, thus increasing the efficiency of the
checking.
To rebuild the RDX files from the DOS command line, enter
RM RDX:<low>-<high>
where <low> is the number of the lowest conference for which
you wish to rebuild the files, and <high> is the number of
the highest.
For previous versions of RoseMail, it made sense to use this
command line in a weekly event. RoseMail 2.00, however, maintains
the RDX files automatically, except at the time of installation of
an update or new verson, when you should ALWAYS rebuild your RDX
files, either from the menu, or by using this command from DOS.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 109
Screen 12. Duplicate checking information.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Duplicate checking information │
│ │
│ Door dupe block : Y │
│ RM dupe block : Y │
│ RoseNet # of msgs : 2000 │
│ │
│ Manual Duplicate Index Rebuild │
│ │
│ Start conference : 0 │
│ Stop conference : 119 │
│ Start RDX rebuild : <ENTER> │
│ │
│ Press ESC (right mouse button) to return to main menu │
│ │
│ The number of messages to keep in the RDX files for RoseNet │
│ duplicate detection purposes. │
│ │
└────────────────────────────────────────────────────────────────┘
Door dupe block
---------------
Set this option if you want to perform duplicate mail checking on
messages that are inserted through the RoseMail door (by
ROMAIL.EXE). Setting this option on will slow down message
insertions slightly, but duplicates will be blocked.
RM dupe block
-------------
Set this option if you want to perform duplicate mail checking on
messages that are inserted from your HUB.QWK packets (by RM.EXE).
With this option on, duplicate mail will be blocked.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 110
RoseNet # of messages
---------------------
The field "RoseNet # of messages" is new with RoseMail 2.00. This
field specifies the number of messages to keep in the RDX files
for RoseNet duplicate detection purposes.
NOTE: When you set RoseMail to block entry of duplicate messages,
keep in mind that very old messages that have been packed out of
your system could be replaced by "new" messages, should you be so
unfortunate as to insert a very old QWK packet, or have a very old
REP packet uploaded to your RoseMail Door. Because you can
control, for each conference, the number of messages for which you
keep records to prevent duplicates (see the Conference Data
screen, under Networks/NetMail, below), this situation should
occur seldom if ever.
Start conference
----------------
This is the lowest-numbered conference to include for the Rosemail
Dupe indeX rebuild.
Stop conference
---------------
This is the highest-numbered conference to include for the
Rosemail Dupe indeX rebuild.
Start RDX rebuild
-----------------
Select this item on the menu and press Enter to start rebuilding
Rosemail Dupe indeX (.RDX) files with the specifications you have
entered for the start and stop conferences. This function should
be executed periodically to remove indexes to deleted messages, to
free up disk space, and to increase performance.
If you are not going to rebuild the .RDX files right now, you can
skip this portion of the menu.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 111
Do "re"-build the RDX files if you have been running PCBoard
previously, that is, if you have message bases already in place,
and you choose to use either of the Duplicate Checking methods.
Do this also if you are upgrading your RoseMail from one version
to another.
OPTIONS
-------
Here, you set your choices for a number of different options.
These are listed below, in the order in which they appear on the
screen. The options set in the example that follows come from a
small test BBS. The illustrated settings are NOT the same as the
default settings. You will want to decide on your own settings.
Here are the categories included on the Options submenu. Remember
that the settings shown here are not the defaults; they represent
a system that has already been configured to the sysop's liking.
Screen 13. RoseMail Options.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ RoseMail options │
│ │
│ Remove REP file : N Max Carbon Copy : 6 │
│ Remove QWK file : N File Downloads : 20 │
│ Remove local REP: Y File Uploads : 20 │
│ Net Sysop Backup: Y Full door usage : 20 │
│ Mark SysOp read : Y Prescan security: 60 │
│ Set mail waiting: Y Max prescan (K) : 2048 │
│ Ignore echo flag: Y Max work size(K): 6000 │
│ Swap to XMS : Y │
│ Swap to EMS : N │
│ Swap to Disk : Y │
│ │
│ Press ESC (right mouse button) to return to main menu │
│ │
│ This is the lowest security level that a user must have in │
│ order to use the prescan function. Prescans are started with │
│ 'ROMAIL /P'. │
└────────────────────────────────────────────────────────────────┘
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 112
Remove REP file
---------------
Set this option to "Y" if you always want your .REP file deleted
before scanning. If this option is set to "N", new messages will
be appended to the existing file. This setting is only used for
netmail transfers.
In other words, if you do NOT delete your HUB.REP file before you
scan for outgoing mail, messages scanned will be added to your
existing HUB.REP packet. It is useful to set this option to "N"
if you repeat scans in between HUB.REP uploads, to pick up the
most recent outgoing messages after you have already scanned once.
If you do choose to have your HUB.REP file deleted, the messages
you scan anew for outgoing mail will be placed into a new HUB.REP
packet. In these circumstances, any existing HUB.REP will be
replaced with the new one at the time you scan.
TIP: If you want to participate personally in any of your hub's
conferences from a network which you do not carry on your BBS, you
can include these conferences in your netmail (HUB.QWK) packet.
If you plan to do this, you may wish to set "Remove REP file" to
"N", so as to include your own replies to local conferences on the
hub in your HUB.REP packet.
NOTE: If you are posting in conferences from a network that
you do carry, you should reply from your BBS, rather than from
your HUB.QWK packet, in order to have your origin tagline
appended properly to your messages. If you are using
RoseReader for Sysops, you can use its Sysop Module to work
"online", yet have all the convenience and features of offline
techniques available to you. Messages you post under your name
by replying from the HUB.QWK will have no origin tagline when
they leave your system, as long as they lie in conferences from
a network you do not yourself carry.
Remove QWK file
---------------
Set this option to "Y" if you want HUB.QWK packets to be deleted
after the messages they contain have been inserted in your message
bases. This setting is only used for netmail transfers.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 113
If you download conferences from your hub that you do not carry
on your own BBS, it is useful to set "Remove QWK file" to "N."
Then you can read and reply in these conferences using your
offline reader. If you do this, you may wish to rename your
HUB.QWK packet immediately after messages have been inserted
from it, so that you do not become confused and try to use the
same packet for a second insertion of messages.
If you are using RoseReader for Sysops, you will find this
method particularly convenient, since you can switch back and
forth between the Sysop module and the offline reader module
without exiting RoseReader You do, however, have to exit your
QWK packet before you can use the Sysop's Module.
Remove local REP
----------------
Set this option if you want locally inserted BBS.REP packets, for
instance, any you upload yourself to your own BBS, to be deleted
after successful insertion.
Net Sysop Backup
----------------
Set this option if you want automatic backups of Net Sysop network
addresses, selected conferences, conference access, message
pointers, and so forth. This flag must be set to Yes to allow
correct restoration of Net Sysop information. This backup aids
you, not to mention your net sysops, if your USERS.INF file is
lost or corrupted.
Mark SysOp read
---------------
If you want messages to sysop that you download using RoseMail to
be marked as read, set this option to "Y."
Set Mail Waiting
----------------
Set this option if you want to update the PCBoard mail waiting
flag whenever a message is inserted. This option may slow down
performance slightly.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 114
If you set this option to Yes, your callers will receive the
PCBoard Mail Waiting notice when they log on. The notice appears
only once; if callers log on and receive the notice, but do not
download the message(s) concerned, they will not be notified a
second time of the same mail waiting. The idea of this flag is to
alert callers to the presence of new mail, rather than to ensure
that they actually read it.
Ignore Echo Flag
----------------
Set this option to Yes to force all netmail to be inserted when
using RM <packet_name> /I, regardless of the message's echo
status.
Some mail doors do not treat the echo flag in the same way
RoseMail does. If your hub does not have a RoseMail Door, you may
need to set this option to Yes. When you set this option to Yes,
this will force insertion of messages when the echo flag is set on
the messages on your hub but the echo flag information is not
transferred to you in the HUB.QWK packet.
We imagine that normally a caller's setting of the echo flag on
messages will be respected by both hub and net sysops. If you are
in doubt as to a caller's settings, you can check with your hub
sysop, or you can call your hub and check the echo status of
downloaded messages while online in PCBoard.
NOTE: You may encounter situations where messages read online in
PCBoard show no ECHO flag set, but where the sysop has set a
conference flag to force all messages in that particular
conference to be echoed. RoseMail and some other mail doors
provide this option to the sysop. Once again, it is up to a sysop
to inform callers which conferences force all messages to be
echoed, so that a caller who does not want a message broadcasted
over the net does not inadvertently leave that message in a
conference where the echo flag is forced on.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 115
Swap to XMS
-----------
If you are running in low memory conditions, and you have EXTENDED
memory, set this option to gain more memory when performing
shelled programs such as PKZIP and DSZ. XMS is the fastest of the
swapping techniques but it requires that you load a HIMEM.SYS
driver in your CONFIG.SYS file.
Swap to EMS
-----------
If you are running in low memory conditions and have EXPANDED
memory, set this option to gain more memory when performing
shelled programs such as PKZIP and DSZ.
Swap to Disk
------------
If you are running in low memory conditions and do not have any
XMS or EMS, set this option to gain more memory when performing
shelled programs such as PKZIP and DSZ. Disk based swapping is
the slowest of the swapping techniques.
Tip on Swapping Techniques
--------------------------
If you set all three of the Swap options to "Y", RoseMail will
choose the fastest swapping method for which enough memory is
available to make the entire swap, and if enough memory is not
available, RoseMail will swap to disk.
For example, if you have enough XMS (Extended memory, the fastest
method), RoseMail will swap to XMS. If not enough XMS is
available to swap everything, RoseMail will swap to EMS (Expanded
memory). If not enough EMS is available, then RoseMail will swap
to disk.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 116
Max Carbon Copy
---------------
This is the number of carbon copies of a single message, not
including the original, that a user is allowed to insert. This
setting only works with RoseReader. PCBoard does not currently
(version 14.5a) have a setting that affects the number of carbon
copies a caller can send.
Note: Allowing or disallowing carbon copies is configurable in
PCBSetup, under Options #1. RoseMail operates independently of
this setting; that is, if you allow Carbon Copies in RoseMail,
these will be inserted when uploaded in a BBS.REP, or when
inserted from a HUB.QWK, regardless of the setting you chose in
PCBSetup.
File Downloads
--------------
This is the minimum security level that a user must have in order
to download files other than mail packets through RoseMail.
File Uploads
------------
This is the minimum security level that a user must have in order
to upload files other than mail packets through RoseMail.
Prescan Security
----------------
This is the minimum security level that a user must have in order
to use the prescan function. You start a prescan by using the
command "ROMAIL /P".
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 117
Max prescan (K)
---------------
This is the maximum amount of disk space (approximate), per user,
that a prescan packet can use (in Kilobytes, when the packet is in
its expanded size). You will want to keep this size in mind for
planning your event, if you prescan packets for net sysops or
other callers during your event.
Max Work Size (K)
-----------------
This is the maximum amount of disk space (approximate), per user,
that can be allocated in the work space. (in Kilobytes). You will
want to set this size according to how many users can be online at
a time using your RoseMail door to take mail packets. Remember to
allow enough space for additions to mail packets such as Magazines
and Add-in files. Remember that this size is for EXPANDED files.
ROSENET INFORMATION
-------------------
Select RoseNet Information from the main menu of the RoseMail
System Manager. Your screen will look something like this:
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 118
Screen ##: RoseNet Information configuration
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ │
│ RoseNet Files/Identifier │
│ Options │
│ RoseNet Pack │
│ │
│ │
│ Press ESC (right mouse button) to return to main menu │
│ │
│ Enter file locations to be used for RoseNet information and │
│ your RoseNet identifier. │
│ │
│ │
└────────────────────────────────────────────────────────────────┘
When you select RoseNet File Information, your screen will look
something like this:
Screen ##: RoseNet File Information screen
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ RoseNet File Information │
│ │
│ RoseNet Dir : C:\PCB\ROSE\DM\ │
│ RoseNet Ident : THYME │
│ RoseNet Log file: C:\PCB\ROSE\DM\LOG │
│ RoseNet Monitor : C:\PCB\ROSE\MONITOR.DAT │
│ RN Bulletin 1 : C:\PCB\GEN\BLT5 │
│ RN Bulletin 2 : C:\PCB\GEN\BLT6 │
│ │
│ Press ESC (right mouse button) to return to main menu │
│ │
│ The directory to store all messages and files associated with │
│ RoseNet and direct mail. │
│ │
└────────────────────────────────────────────────────────────────┘
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 119
The RoseNet Dir is the one in which you keep the MAP files for the
RoseMail routing system. Commonly, this directory is called
C:\PCB\ROSE\DM, where "DM" stands for "Direct Mail". Note that
updates to your MAP files come to you automatically from the next
system up from you in the mail routing link When a new DM.ZIP
file arrives, containing the new maps, you unzip the file in your
C:\PCB\ROSE\DM directory (or equivalent). This updates your mail
routes.
RoseNet Ident is the identifying name given to your system for
RoseNet Mail. You arrange for this name with the RoseNet Central
Host (Vic Kass), Rose Media BBS. This name is the one that is on
the MAP files that control the routing of RoseNet mail.
RoseNet Log File is the directory in which you store log files and
other information generated from RoseNet message traffic.
RoseNet Monitor is the file name and location for your RoseNet
Monitoring file. This file allows you to select users that you
want to monitor RoseNet messages to/from as well as being able to
block message to and/or from. Press F2 to edit this list. Leave
the field blank to disable checking.
The fields for Bulletins allow you to provide file names and
locations in which you wish to store information on changes to
RoseMail. You can set these filenames to match PCBoard bulletin
filenames; if you do so, these bulletins will be updated
automatically when you receive replacements in your QWK files.
You may receive bulletins on:
- Changes to RoseMail
- How to use RoseMail
- Changes to RoseReader
- How to use RoseReader
After you have configured this area, you should make sure the
directories you have specified for these files exist on your
system. If you wish to receive the bulletins as PCBoard
bulletins, create bulletin files, perhaps adding a title, and use
PCBSetup to specify their location and to edit your list of
Bulletins. For instance, if you will carry these bulletins on
your Main Board, you would choose Main Board Configuration from
the PCBSetup main menu.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 120
The next screen you will work with is RoseNet Options. Here you
indicate whether you will accept encrypted RoseNet messages on
your system, whether you wish to track your RoseNet operations
with log files, and the maximum size of a file you will permit to
be passed through your system as an attachment to a RoseNet
message.
Screen ##: RoseNet Options
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ RoseNet options │
│ │
│ No RN encrypt : Y Max incl file(K): 30 │
│ Log RN files : Y │
│ │
│ │
│ Press ESC (right mouse button) to return to main menu │
│ │
│ If you want to disable the passage of encrypted RoseNet │
│ messages on and through your system, set this option to YES. │
│ All attempts to do so will result in the message being bounced │
│ back to the originator. │
│ │
└────────────────────────────────────────────────────────────────┘
Select various options for RoseNet.
No RN encrypt: If you want to disable the passage of encrypted
RoseNet messages on and through your system, set this option to
YES. This will cause encrypted message sent to your system to be
returned to the writer. The message will not remain on your
system, and the writer will receive an explanation.
Log RN files: Set this option if you want a log of all attached
files that are sent via RoseNet. You must also make sure that you
have a log directory defined under RoseNet Files.
Max incl file (K): This is the largest file size that can be
attached to a RoseNet message.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 121
The next item on your screen is the RoseNet Pack. See Screen ##
to see what it looks like. This is an Action menu; you start a
RoseNet pack by pressing Enter with the field highlighted.
When you start a RoseNet Pack, you remove old RoseNet messages.
RoseMail will remove old RoseNet messages automatically for active
users of RoseNet, but requires this pack to remove messages for
expired and inactive users.
NETWORKS/NETMAIL
----------------
General Information
-------------------
Networks/NetMail is the network mail submenu. It allows you to
set available networks on your board, to define what conferences
belong to each network, and to set up individual net sysop access.
This submenu is enabled at the time you register, when you install
your ROSEMAIL.KEY file.
Arranging to carry netmail
--------------------------
You decide what network mail you are going to carry, and make your
own arrangements with the network administrator, and with your hub
sysop.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 122
How RoseMail handles netmail
----------------------------
All network mail, that is, mail that you send from your BBS to
other BBSs, and mail that you take down from other BBSs and insert
in your message bases, is contained in conferences you define in
PCBSetup as "Echo" conferences. Normally, individual messages
placed in these conferences must have their echo flags set in
order to be scanned by RM.EXE and inserted into the HUB.REP mail
packet. That is, if a caller posts a message that does not have
its echo flag set, that message will not be included in the
HUB.REP packet that you scan from your BBS unless you have set
Conference Flag 14, force all messages in the conference to be
echoed, for the conference concerned.
RoseMail Echo Mail Features
---------------------------
Public echo mail
----------------
Network mail consists of messages placed in echoed conferences
that have their echo flags set, and of mail in a conference
where you have forced all messages to be echoed by setting
Conference Flag 14 for that conference. Usually these messages
are public, although RoseMail provides a setting (Conference
Flag 5) that allows the sending of "private" (personal) echo
messages as well.
You define a conference as having echo mail, or not having it,
in the Conferences submenu of PCBoard's PCBSetup program. You
can also set RoseMail's Conference Flag 14 to force all
messages in an echo conference to be echoed regardless of the
setting a caller places on the message.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 123
Echo flag
---------
At the time of this writing (March 1992), most offline mail
readers do not deal specifically with the echo flag on
messages. RoseReader is an exception; it provides a means
for callers to turn the echo flag on or off, just as they
would do if entering the messages online in PCBoard, in an
echo conference. RoseMail recognizes both the sysop's
setting in the conference (in PCBSetup), and the caller's
setting of the echo flag.
Control which messages in a conference shall be echoed
------------------------------------------------------
You, the sysop, set the echo status of a conference in
PCBSetup.
As a subset of your designation, a caller leaving a message in
an echo conference can turn off the echo flag on his or her
message.
When RM.EXE scans for mail, it will normally respect the
caller's designation. Messages in echo conferences with their
echo flags set will be scanned and added to your HUB.REP
packet; messages with their echo flags turned off will not be
included in the packet, unless you have set Conference Flag 14
for the conference in which the message is posted.
When you specify in PCBSetup that a conference will not echo
mail, that makes the conference local to your board. RM.EXE
will not scan such a conference for outgoing mail. Callers
cannot set echo flags on the messages they leave in a local
conference.
Your callers might like to be aware that when you, the sysop,
set Conference Flag 14, forcing all messages in a conference to
be echoed, RoseMail overrides the setting visible online in
PCBoard. You might wish to provide a bulletin listing such
conferences.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 124
Personal Echo Mail
------------------
In the RoseMail System Manager, you can set Conference Flag 5
on an echo conference to allow it to accept "Personal Echo"
mail. In conferences you have set to allow personal echo
mail, callers who leave messages can flag their messages both
as "echo" and as "personal" ("private"). When you scan for
mail with RM.EXE from a conference set to allow Personal Echo
mail, messages with the echo flag set, whether personal or
not, will be added to your HUB.REP packet. If you are
inserting messages from a HUB.QWK packet, messages flagged as
both Personal and Echo will be inserted in conferences where
you have set Conference Flag 5.
If you have not yet registered RoseMail, you do not have a
ROSEMAIL.KEY file, and you may skip the following section, and go
to the last item on the menu, Exit (and Save). When you save your
configuration, your RoseMail Door will be in operating condition
for your local callers.
CONFIGURING NETWORKS/NETMAIL
----------------------------
Special care needed with numbers
--------------------------------
You need to take considerable care when entering numbers in
your netmail configuration. Mistakes may cause messages to
fail to echo, or, perhaps worse, to be dumped into the wrong
conferences. You will, then, want to proofread your number
entries carefully.
Pay particular attention to:
- Numbers you enter as Host Names (or Addresses)
- Numbers you enter under Conference Ownership
- Numbers you enter as Network Translations
Select Networks/NetMail from the RoseMail System Manager's Main
Menu.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 125
The Networks/NetMail Menu
-------------------------
When you select Networks/NetMail from the Main Menu, the first
screen you see is a list of submenus. It looks something like
this:
Screen 18. Networks/NetMail Main Menu.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Available Networks │
│ Conference Ownership │
│ Net Sysop Access │
│ Network translations │
│ Taglines │
│ Logging files │
│ Pointer Resets │
│ USERS.INF Reset │
│ │
│ Press ESC (right mouse button) to return to main menu │
│ │
│ Network names and your network address for netmail transfers. │
│ │
└────────────────────────────────────────────────────────────────┘
The categories listed are:
Available Networks
------------------
This screen shows network names and your network address for
netmail transfers. The address that shows on your screen here
can be treated as a node ID if desired (see "Available
Networks", below, for more information).
Conference Ownership
--------------------
Here, you define what network each conference belongs to.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 126
Net Sysop Access
----------------
Here, you add or change netmail status for net sysops, and
define access to your RoseMail Door (yes or no) for all your
registered users (not just sysops).
Network translations
--------------------
Your networked (echo) conference names are listed here
automatically; RM.EXE finds them for you. In this area, you
tell RoseMail what conference numbers on the host system (the
one you call for mail) correspond to your own conference
numbers.
You can also use this submenu to set message pointers manually
for scanning outgoing mail into your HUB.REP packet, in case
you want to alter your normal scan.
"Last Read" message numbers that show in the Network
Translations area are updated automatically when you scan for
outgoing mail, and also when you reset pointers from the
Pointer Resets submenu under Networks/NetMail.
Taglines
--------
Here, you define taglines for netmail originating on your
board. These are taglines that will be appended to all PCBoard
messages scanned with the "RM <hubpacket> /S" command to go out
from your system in a HUB.REP packet, or that are downloaded by
a net sysop who calls your system for mail, thus picking up a
BBS.QWK from your system. In short, this is the area where
you, the sysop, control the appearance and content of all your
own taglines. (See also the tagline area under the "Available
Networks" submenu; that area is set up to deal with mail
packets from your hub that arrive on your system with messages
that have originated on the hub that carry no origin taglines.)
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 127
Logging files
-------------
Here, you enter the names and locations of files you will use
as logs to track your RoseMail operations.
Pointer Resets
--------------
Here, you reset your network message pointers, if you need to
repeat scans for outgoing mail from your BBS because a REP
packet has been lost or destroyed in some way.
USERS.INF Reset
---------------
Here, you restore message pointers, selected conferences,
PCBoard conference registration flags and all RoseMail door
information for net sysops. Do not do this casually! To use
this feature, you must have set the Net Sysop Backup option to
YES under the RoseMail Options submenu.
HOW TO CONFIGURE AVAILABLE NETWORKS
-----------------------------------
Available Networks
------------------
In this submenu, you will find some pre-defined nets, and some
slots reserved for later expansion. Besides these, slots are
provided for you to define your own nets, in association with
other sysops.
If you are carrying only networks that are already defined, all
you have to do in the submenu entitled "Available Networks" is
enter the mail packet name, the compression selection letter,
and your hub sysop's RoseReader serial number (in the last four
digits of the series of zeros, leaving the other zeros as they
are). If your hub sysop does not have RoseReader, you leave
the "Host Name" field untouched.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 128
When you select Available Networks, you will see something like
the following.
Screen 19. Available Networks.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Networks available │
│ │
│ Network name Packet Comp Host Name │
│ 1. RoseNet ROSE Z 00001001 │
│ 2. Usenet 00000000 │
│ 3. U'NI-net ROSE Z 00001001 │
│ 4. SmartNet 00000000 │
│ 5. QuebecNet 00000000 │
│ 6. Intelec 00000000 │
│ 7. BizNet 00000000 │
│ 8. Throbnet 00000000 │
│ 9. ILink 00000000 │
│ 10. Dev-Net 00000000 │
│ │
│ Press ESC (right mouse button) to return to net menu │
│ │
│ The name of the packet to use for transfering mail on this │
│ network. │
│ │
│ Press <F1> for information on network. │
│ Press <F2> to edit hub information. │
│ │
└────────────────────────────────────────────────────────────────┘
This screen contains the following fields:
Network number
--------------
This is the number of the network. Some networks are
pre-defined, some are reserved, and the remaining ones can be
whatever you and your fellow sysops designate.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 129
Network name
------------
This is the name of the network.
Packet
------
This is the mail packet name for the system you call for
mail.
Comp
----
This is the selection letter of the compression program that
you have selected for use on the system that you call for
mail. It applies to your HUB, not to your own system. If
you change your selection on the hub, you must change it here
as well.
Host Name
---------
This is the RoseReader serial number of your hub sysop. Use
the last (rightmost) four digits in the set of eight zeros,
and leave the leftmost four zeros in place as they are.
If your hub does not have RoseMail, leave this field set all
to zeros, as it comes by default.
IMPORTANT NOTE! DO NOT put your own RoseReader serial number into
the Host Name field. Doing so could cause the infamous
"unpredictable results." Your RoseReader serial number serves as
your RoseNet address, and so is public along the RoseNet routed
links. This same number appears to a caller who opens your
RoseMail Door, right below the RoseMail logo. This allows your
callers to be aware of how to route mail using the RoseNet system.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 130
Pre-defined nets
----------------
The network numbers and names are already provided for the
pre-defined nets. Your TAB and Shift-TAB keys will not take
you to these areas.
Wide beta note, Sat 6 Feb 1993, 16:30: There may be something you
can enter under Host Name for a non-RoseMail hub sysop. If so,
Drew Miller, help! :-)
For each of the pre-defined nets from which you carry mail,
you will need to define the packet name (the "HUB" part of
"HUB.QWK" or "HUB.REP"), and the compression method you use
on that BBS (identify this by letter). For all RoseMail
Doors from which you take mail, you will need to enter the
last four digits of the hub sysop's RoseReader serial number
to replace the rightmost four zeros under "Host Name". Where
your hub does not run RoseMail, you will leave the "Host
Name" field untouched.
Wide beta NOTE: At the time of this writing (Fri 5 Feb 1993,
19:51), the file NETWORK.DES, which provides information on
networks, is not yet available. You will get a message to this
effect if you press F1 from this screen.
The field labeled "Edit hub information" is new with RoseMail
2.00. This area was included in order to allow tagging of
messages that originate on your hub, when those messages come from
a mail door that does not tag messages that originate on the hub.
The feature provides compatibility with doors such as Qmail and
many of its clones. RoseMail appends taglines to messages that
originate on the hub at the time a net sysop downloads the packet
through RoseMail, and it also tags messages that a net sysop scans
into a HUB.REP packet.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 131
Because the hub's taglines are provided by RoseMail at the time of
download by the hub sysop, and the node's taglines are provided at
the time of the scan into a HUB.REP by the node sysop, RoseMail,
in contrast to other mail software, allows the sysop of each board
to control the taglines right at the source, or the origin, of the
message. Still, compatibility with software that shunts control
onto the node sysop requires that you, the RoseMail sysop, be able
to insert the SYSOP name of your hub sysop on messages that may
arrive with the To or the From fields containing "SYSOP", and also
that you be able to tag messages that originated on the hub, and
come down without origin taglines.
So, the F2 key allows you to insert the necessary information,
thus to download HUB.QWK packets from Qmail and other doors that
shunt tagline and SYSOP name control to the node.
F2: Edit hub information. In this area, you enter the name of
your hub sysop, in the form it is used on the hub, and you enter
the tagline your hub uses, usually as your hub sysop directs.
Tip: The origin tagline serves to help trace lost or stray
messages. If your hub is a RoseMail system, the messages that
arrive in your HUB.QWK will normally be tagged. There are,
however, circumstances, depending on your hub's configuration and
your own, in which messages CAN arrive from your hub's RoseMail
Door without your hub's origin tagline. For instance, if your hub
has omitted to set an echo conference to ECHO in PCBSetup, and you
have "Ignore Echo Flag" set to YES in RoseMail Options in the
RoseMail System Manager, messages will import into your system,
but they could arrive untagged at the hub.
At any rate, echo messages coming in a HUB.QWK from a RoseMail
Door that lack an origin tagline are a sign of misconfiguration
somwhere. Therefore, if you include some single extra symbol in
the tagline you enter in this field, it will reveal a
configuration problem, because you will be able to detect that the
message was tagged at the time of insertion, by your RM <hub> /I
operation. The illustration that follows contains such a symbol
as the first character in the tagline. The illustration is
cramped for reasons of space on paper; you will have slightly more
space to work with.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 132
Screen ##: Edit hub information
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Networks available │
│ │
│ Network name Packet Comp Host Name │
│ 51. EerieNet EARS Z 00002067 │
│ 52. ThymeNet 00000000 │
│ │
│ ┌──────────────────────────────────────────────────────────┐ │
│ │ Edit Board Information │ │
│ │ │ │
│ │ Hub sysop: JULIANNE FISCHER │ │
│ │ Hub tagline: σ EerieNet * AllEars BBS * 123-456-7890 │ │
│ │ │ │
│ │ ESC to abort F10 to save │ │
│ └──────────────────────────────────────────────────────────┘ │
│ 59. 00000000 │
│ 60. 00000000 │
│ │
│ Press ESC (right mouse button) to return to net menu │
│ │
│ Enter the sysop's name of your hub system. This will be used │
│ for translations when netmail packets, inserted with RM XXX │
│ /I, are to/from sysop. (Not needed if hub is running RoseMail) │
│ │
└────────────────────────────────────────────────────────────────┘
When you have filled out the Packet, Comp(ression) and Host Name,
and edited the hub information, you have finished the
configuration for pre-defined nets under the Available Networks
menu.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 133
Defining your own networks
--------------------------
To reach a screen where you can define your own networks, use
PgDn, PgUp, and your Down and Up Arrows to scroll the screen,
until you reach the blank areas. You may define your network
in any of the empty slots: those which neither have pre-
defined networks nor say "Reserved" The first free space in
RoseMail 2.00 is Network #41.
In these slots, you can add your own network definitions.
When you have defined a network in cooperation with another
sysop or group of sysops, your configured screen might look
something like this.
Screen 20. Defining your own network.
┌────────────────────────────────────────────────────────────────┐
│ RoseMail 2.00ßSystem Manager (02-04-93 14:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Networks available │
│ │
│ Network name Packet Comp Host Name │
│ 51. EarthNet EARTH Z 00002492 │
│ 52. ThymeNet 00000000 │
│ 53. PACnet EARTH Z 00002492 │
│ │
│ Press ESC (right mouse button) to return to net menu │
├────────────────────────────────────────────────────────────────┤
│ The name of the packet to use for transferring mail on this │
│ network. │
│ │
│ Press <F2> to edit hub information. │
└────────────────────────────────────────────────────────────────┘
When the screen comes up, your cursor highlights the Packet field.
Press Shift-TAB to reach the Network name field. Fill in the name
of your network. The node sysop, the sysop who calls out for
mail, then fills in the Packet name of the hub, the Comp(ression)
selection letter, and the hub sysop's RoseReader serial number, as
illustrated above.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 134
Notice in the illustration that Network #52 contains only the name
of the network. That network is one that the sysop who filled out
the screen hosts; therefore the fields for Packet name,
Comp(ression) and Host Name are left untouched, so as to prevent
"unpredictable results" from plaguing the sysop in question.
NOTES on defining your own networks: See RoseMail operations,
later in this guide, for a summary of the steps you take to set up
your own networks. They include defining your own networks as
described just above, having the hub and central host sysops
assign net status to all node sysops who call their systems for
mail, setting up the conferences using PCBSetup, and, once the
conferences are defined in PCBSetup, running the RoseMail System
Manager, building RDX files for conferences in the new net from
the Duplicate Checking menu, and running the Conference Optimize
routine from the RoseMail System Manager's main menu.
CONFERENCE OWNERSHIP
--------------------
Here you indicate what network a conference belongs to. Your
conferences are listed automatically down the left side of the
screen, and the network numbers run across the top.
See the list of editing keys at the beginning of the Main
Reference section, above, for a description of the editing keys
Ctrl-J, Ctrl-S and Ctrl-C, which will assist you in configuring
this area.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 135
In the screen below, the conferences indicated are all set to the
same network, NET #3.
Screen 23. NetMail conference definitions.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Set NetMail conference definitions - what network a conference │
│ belongs to │
│ │
│ # Conference name 1 2 3 4 5 6 7 8 9 10 11 │
│ 0. Main Board │
│ 1. HelpThyme │
│ 2. NewsReadOnly │
│ 3. Pets │
│ 4. PSRMTSysops X │
│ 5. ChatThyme │
│ 6. AsciiArt X │
│ 7. AnsiArt X │
│ 8. EMail │
│ 9. Un-confer X │
│ 10. Test-RM_SnNet │
│ Press CTRL-J to jump to a conference, CTRL-S/CTRL-C to │
│ set/clear ranges. │
│ │
│ Press ESC (right mouse button) to return to net menu │
│ │
│ Use arrow keys to position the cursor at different conferences │
│ and networks. Press 'X' to set conference in the given │
│ network or <SPACE> to deselect the conference. Pg-Up and Pg-Dn │
│ to see different screens. │
│ │
└────────────────────────────────────────────────────────────────┘
To reach the remaining network numbers, which are off the screen
to the right, press your Right Arrow key or your TAB key. The
Arrow keys will wrap around, so that when you pass Net 64, Net 1
will appear again.
Use your arrow keys to position the cursor at different
conferences and networks. Press "X" to set an individual
conference in the given network or <SPACE> to deselect the
conference individually.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 136
Wide beta NOTE, Sat 6 Feb 1993, 17:56: The following paragraph
may need to be changed, as the possibility of cross-echoing
conferences is implemented.
If you are changing the network a conference belongs to, when you
set the new network flag, the previously set flag is automatically
reset (disabled).
Use PgUp and PgDn to see different screens.
NET SYSOP ACCESS
----------------
All registered users are listed under Net Sysop Access.
Relatively few of your users will be taking mail from you. You
should only configure Net Sysop Access for sysops who call you for
mail. You can, however, use the Net Sysop Access menu to change
the status of ANY user's access to RoseMail from Yes to No or vice
versa. Do not enter any address in your own, (SYSOP) record in
this area, since you are not acting as a net sysop on your own
system, and entering address information in your own record here
can produce "unpredictable results".
Net Sysop Address
-----------------
Fill in the RoseReader Serial Number for each net sysop who
calls your BBS for mail. You will need to obtain this number
from the net sysop. A net sysop's RoseReader Serial number can
be seen on RoseReader's opening screen. Also, a sysop running
RoseMail can see the same serial number by logging into the BBS
locally and opening the RoseMail Door. The serial number shows
just under the RoseMail logo. If no sysops call you for
network mail, you do not have to fill out this screen.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 137
Screen 24. Net Sysop Access.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Set Netmail addresses for Net Sysops │
│ │
│ User Name : THORNTON THISTLE Serial # : 00000000 │
│ 1 RoseNet N │
│ 2 Usenet N │
│ 3 U'NI-net N │
│ 4 SmartNet N │
│ 5 QuebecNet N │
│ 6 Intelec N │
│ 7 BizNet N │
│ 8 Throbnet N │
│ │
│ │
│ CTRL-PgUp for previous user, CTRL-PgDn for next user, CTRL-F │
│ to find user. │
│ │
│ Press ESC (right mouse button) to return to net menu │
│ │
│ Select the networks that this user is granted net sysop status │
│ in. NOTE: You should NOT set yourself as a net sysop. │
│ │
└────────────────────────────────────────────────────────────────┘
NETWORK TRANSLATIONS
--------------------
For a sysop setting up netmail for the first time, this area is
one to be treated with great respect and considerable
cross-checking, to make sure you have the numbers set correctly.
Mistakes made in this area, such as typing the wrong numbers, may
cause you to dump messages into the wrong conferences. Such
errors can be most embarrassing, so please check your typing. You
will probably be most comfortable if you work from a written list.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 138
If you already have conference translation tables set up in Qmail
or a Qmail-compatible door, you may be able to use the conversion
program that comes with RoseMail 2.00. This program will convert
Qmail and compatible network translations, so you can avoid, when
possible, having to type the numbers of conferences on your hub
system during a change from different net software. Naturelly,
being a RoseMail Sysop, you are very conscientious and choosy
about how neatly and cleanly your system operations, so you will
test your translations before actually sending a HUB.REP packet -
just in case one of the conference translations has gone wrong.
After all, YOU will never be embarrassed by dumping messages into
the wrong conference.
A sample translation screen follows. You will need to enter
translations for each conference you carry from your host system.
In the simulated screen shown below, the list of your Conference
Numbers and Conference Names is taken automatically from your
PCBoard configuration. Similarly, the last column, "Highest in
base," comes from your PCBoard files, and you do not have to,
indeed, you cannot, change that number directly.
The numbers in the "Last Read" column indicate where the current
message pointers lie after the last scan from your system for
outgoing mail.
To change the numbers in the "Last Read" column, you can use the
Pointer Reset submenu, which will reset all your pointers to the
position they were in at the date and time you select from the
list displayed.
Also, you can change these pointers manually, by typing in message
numbers yourself. You might wish, for instance, to reset your
pointers in a single conference this way, to repeat a scan for
outgoing mail in that conference only.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 139
Screen ##: Prompt for network in which to enter translations
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Set translation codes for network │
│ # Conference name Translation Last read Highest in base │
│ │
│ ┌────────────────────────────────────────────────────┐ │
│ │ Network number to set translation for: │ │
│ └────────────────────────────────────────────────────┘ │
│ │
│ Press CTRL-PgUp for previous network, CTRL-PgDn for next │
│ network │
│ │
│ Press ESC (right mouse button) to return to net menu │
│ │
│ Set the conference number of the board that you are sending │
│ netmail to which corresponds to each of your conferences. │
│ │
└────────────────────────────────────────────────────────────────┘
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 140
Screen 25. Set translation codes for network mail.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Set translation codes for network PACnet - NET 53 │
│ # Conference name Translation Last read Highest in base │
│ 17. Beginners-PN 9 442 442 │
│ 18. PACAdmin-PN 2 71 73 │
│ 20. PC-Mania_PN 8 34 36 │
│ 23. CompuChat-PN 10 18 19 │
│ │
│ Press CTRL-PgUp for previous network, CTRL-PgDn for next │
│ network │
│ │
│ Press ESC (right mouse button) to return to net menu │
│ │
│ Set the conference number of the board that you are sending │
│ netmail to which corresponds to each of your conferences. │
│ │
└────────────────────────────────────────────────────────────────┘
NOTE: The first two columns, "#" and "Conference name, are set
automatically from your PCBoard conference configuration.
Translation
-----------
For each conference you bring in from your host (HUB) BBS, in
the Translation column, beside the number and name of your own
conference, enter the corresponding number of the host
conference. It helps to have a written list which shows the
numbers of your conferences and the numbers of those same
conferences on the host BBS.
Last read
---------
This is the last message that was scanned on your board.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 141
You can change this number manually, either to rescan messages
previously scanned, or to pass by messages you decide not to
scan.
You can set "Last Read" pointers back in all scanned
conferences for a net at once by using the Pointer Resets
submenu off the main Networks/NetMail menu and choosing the
appropriate date and time from which to repeat a mail scan.
RoseMail keeps up to 10 records of previous scans for each
network, in .PTR files which are located in a subdirectory that
RoseMail creates automatically off your \PCB\ROSE directory.
This subdirectory is \PCB\ROSE\NET.
Highest in base
---------------
This is the high message number on your system for this
conference. This number is read from your PCBoard files, and
can only be changed by using PCBPACK (or some similar program)
and renumbering your messages. It is not recommended that you
renumber unless forced to by loss of message bases, because
renumbering nullifies the message pointers of your callers.
Network Translations: change networks
--------------------------------------
To change from one network to another, so that you can fill in the
network translation numbers, or set your "Last Read" message in a
conference manually, press Ctrl-PgDn or Ctrl-PgUp, depending on
whether you wish to scroll upwards or downwards.
TAGLINES
--------
Here you enter the origin taglines that are to be added to
messages leaving your BBS.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 142
Screen 26. Network taglines.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 1.70 System Manager (02-24-92 16:00) │
│ Copyright (C) 1991, 92 Rose Media Incorporated │
│ │
│ Network taglines │
│ │
│ Network name Tagline │
│ 41. Ghostnet Ghostnet * Wood BBS * Kayaust, BC 604-999-1234 │
│ 42. HerbNet HerbNet * Wood BBS * Kayaust. BC 604-999-1234 │
│ 43. FishyNet FishyNet * Wood BBS * Kayaust, BC 604-999-1234 │
│ 44. │
│ 45. │
│ │
│ Press ESC (right mouse button) to return to net menu │
│ │
└────────────────────────────────────────────────────────────────┘
Enter the text you want added to netmail messages originating on
your board.
NOTE: Do NOT enter "RoseMail 2.00:" This is added to your
taglines automatically. Begin, then, with the name of the
network, and follow with your BBS name, your location, and your
BBS phone number.
POINTER RESETS
--------------
To reset the pointers for all conferences on a net that you scan
for outgoing netmail from your BBS, select Networks/NetMail from
the main menu of the RoseMail System Manager, and then select
Pointer Resets from the submenu. If you wish to reset pointers
individually for individual conferences, use the Network
Translations menu to reset the "Last Read" messages manually.
Wide beta note, Sat 6 Feb 1993, 18:16: Pointer files have changed
since version 1.70. This area of the documentation is to be
updated.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 143
When you select Pointer Resets, you see a list of dates and times.
These are provided by the files RESETnn.PTR, which are created
automatically when you scan for outgoing mail. RoseMail saves up
to twenty-five of these files, in the subdirectory that RoseMail
creates automatically off your \PCB\ROSE directory, called
\PCB\ROSE\NET. The RESETnn.PTR files are maintained automatically
by RoseMail.
You can choose a date and time to which you wish to reset your
message pointers, so as to repeat a scan of your board that you
made before. When you tell the RoseMail System Manager to reset
your pointers, you are asked whether you want to set your pointers
to before or after the date and time you selected.
Screen 27. Pointer Resets.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 1.70 System Manager (02-24-92 16:00) │
│ Copyright (C) 1991, 92 Rose Media Incorporated │
│ │
│ Reset Message pointers │
│ │
│ Packet Date Packet Time │
│ 01-03-1992 21:12 │
│ 01-03-1992 18:02 │
│ 01-02-1992 22:16 │
│ │
│ Press ESC (right mouse button) to return to net menu │
│ │
└────────────────────────────────────────────────────────────────┘
Use the cursor keys to select the packet date and time to which
you want to reset your pointers. Press Enter to select or ESC to
abort the change.
Screen 28. Choose to set your pointers Before or After the
selected date and time of scan.
┌────────────────────────────────────────────────────────────────┐
│ │
│ Reset message pointers to B]efore or A]fter scan │
│ (ESC to abort)? │
│ │
└────────────────────────────────────────────────────────────────┘
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 144
USERS.INF RESET
---------------
You must have had Net Sysop Backup, under RoseMail Options, set to
YES, if you are to reset net sysop information under this submenu.
This is not something you do casually. However, if you need to
reset your USERS.INF file because of loss or corruption of files,
select Networks/NetMail from the main menu of the RoseMail System
Manager, and from the submenu, select USERS.INF Reset.
Enter the name of the net sysop for whom you want to restore
information. You may reset this information for all net sysops by
typing "ALL" instead of an individual name. Restoration includes
message pointers, PCBoard conference registration, PCBoard expired
conference registration, PCBoard scan preference and all RoseMail
information. When resetting "ALL" (all users at once), we
recommend that you take the board down first.
If the name that you type cannot be found, you will be given a
message to that effect, and you will be allowed to try again.
Screen 29. USERS.INF Reset.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 1.70 System Manager (02-24-92 16:00) │
│ Copyright (C) 1991, 92 Rose Media Incorporated │
│ │
│ │
│ User Name (or ALL): _ │
│ │
│ │
│ Press ESC (right mouse button) to return to main menu │
│ │
└────────────────────────────────────────────────────────────────┘
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 145
CONFERENCE DATA
----------------
Use this menu to specify the number of messages you wish to track
for duplicate checking in each conference, and to set flags for
each conference to affect its accessibility to the caller. You
can force a conference to be scanned, you can specify whether a
conference's messages are all to be personal, public, or echoed,
you can add conference bulletins, add conference files, and so
forth. See the individual explanations below for details.
Once you have set conference flags to define accessibility for the
caller, the caller will still have to select the items in RoseMail
in order to receive them in the mail packet.
The following simulated screen is partly filled out. This screen
comes from a small test version of a BBS. Your own conferences
will be listed automatically when this screen comes up. You can
access a continuing listing of your conferences by pressing PgDn.
The "X"s shown in the following simulated screen were inserted by
the sysop of the test BBS just mentioned. By default, the screen
comes up with no flags set.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 146
Screen 16. Set conference data.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Set conference data │
│ # Conference name #M 1 2 3 4 5 6 7 8 9 10 11 │
│ 0. Main Board 2000 X X X X X X │
│ 1. HelpThyme 2000 X │
│ 2. NewsReadOnly 2000 X X X X X │
│ 3. Pets 2000 │
│ 4. PSRMTSysops 2000 X X X X X X │
│ 5. ChatThyme 2000 │
│ 6. AsciiArt 2000 │
│ 7. AnsiArt 2000 │
│ 8. EMail 2000 X X │
│ 9. Direct-Mail 2000 X X │
│ 10. Test-RM_SnNet 2000 X │
│ │
│ Press CTRL-J to jump to a conference, CTRL-S/CTRL-C to │
│ set/clear ranges. │
│ │
│ Press ESC (right mouse button) to return to net menu │
│ │
│ Enter the number of messages to store in the RoseMail │
│ Duplicate Indexes for this conference. │
│ │
└────────────────────────────────────────────────────────────────┘
See the list of keys near the beginning of the main reference
section for a description of the special editing keys Ctrl-J,
Ctrl-S, and Ctrl-C that will assist you in configuring these
flags.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 147
The "#M" field specifies the number of messages you wish to track
in the RDX (RoseMail Duplicate IndeX) files to keep duplicate
messages from entering your system. As you can see, you can set
this number individually for each conference. This feature is new
with RoseMail 2.00. The RDX files are maintained automatically,
except at the time of initial installation of RoseMail, or at the
time you install an update or upgrade. When you install an update
or upgrade, you should rebuild all the RDX files, either from the
DOS command line (see the Command Summary near the end of this
guide), or you can use the Duplicate Checking menu to rebuild
them. When you change the number of messages for a conference,
you should rebuild the RDX file for that conference. Once more,
you can use the Duplicate Checking menu, or you can use a DOS
command to rebuild the RDX file.
The flags have the following effects:
Flag 1: Force this conference to be scanned
Force this conference to be scanned even if the user has not
selected it. Note: The user must still have sufficient
security to access the conference.
Flag 2: Insert all messages as personal
Flag 3: Insert all messages as public
Flag 4: Deny all insertion attempts
Only the sysop can insert messages in a conference where this
flag is set; this flag makes the conference "read-only" for
all other users.
Flag 5: Allow personal echo mail
Personal echo mail is private mail with the echo flag set on
the message(s). For this flag to take effect, you must have
used PCBSetup to allow echo mail in the conference for which
you set this RoseMail flag.
Flag 6: Include new bulletins
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 148
Flag 7: Include upload file listings
Upload file listings are lists of files that have been
uploaded to the conference concerned since the last time the
caller took down a mail packet from RoseMail. Note that to
obtain these listings, the caller must have the conference
selected from which these listings are available in PCBoard.
Callers who do not wish to read mail in the conference
concerned may select it for their Personal mail only. See
the Caller's Guide to RoseMail, Option 6, for more detail.
Flag 8: Continue file scans past "old" files
Permit the scan for file listings to continue even if the
scan finds a file on which the date is older than the date of
the caller's last RoseMail download.
You should set this flag if your files for the conference in
question are sorted in any order other than reverse date.
Check the Main Board Configuration, or Conferences, under the
PCBSetup utility, to find out what sort order you have
specified for the files in the conference.
Flag 9: Include the NEWS file
Flag 10: Force the NEWS file
If you set this flag, you should also set Flag 1 for this
conference, to make sure callers receive the NEWS file in
their mail packets.
Flag 11: Include download file listings
If you set this flag, listings of all new files that have
been added since the caller's last RoseMail download are
available for the caller's mail packet. To obtain these
listings in the packet, the caller must select the conference
from where these listings are available in PCBoard.
Callers who do not wish to read mail in the conference
concerned may select it for their Personal mail only. See
the Caller's Guide to RoseMail, Option 7, for more detail.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 149
Flag 12: Allow aliases
Do not check the name in the FROM field on uploaded messages.
Flag 13: Ignore PCBoard private flag
If you set this flag for a conference you have marked private
using PCBSetup, the conference will appear in the Conference
Selection screen for a caller who has a sufficient security
level as defined in PCBSetup. Also, if selected by the
caller, the conference will appear in the caller's download
scan in RoseMail. Callers with insufficient security levels
for the conference, as defined in PCBSetup, will not see the
conference in the Conference Selection screen, so will be
unable to select it.
Flag 14: Force echo flag on
All messages in this conference will be echoed, regardless of
the echo status of individual messages callers post in it.
If a caller leaves a message in the conference that is not
designated ECHO, no ECHO flag will show when the message is
read online in PCBoard. The message is forced to ECHO status
at the time of the RM.EXE mail scan for a REP packet. The
ECHO flag is forced on at this time, so it can be seen if you
review your HUB.REP packet from your HUB.QWK packet using
RoseReader for Sysops.
Flag 15: Force message date/time to time of insertion.
All messages added to a conference in which you set this flag
will have in their headers the date and time at which they
were posted on your system instead of the date and time they
were written.
Flag 16: Force this conference to be scanned (Personal or All)
Force this conference to be scanned even if it is not
selected by the user. Will scan for personal mail only,
unless the user has ALL configured. Note: The user must still
have sufficient security to access the conference.
Flag 17: Strip ANSI codes in incoming messages.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 150
USER FLAGS
----------
Set individual user flags for each conference. These have nothing
to do with net sysop access. Use the Networks/NetMail submenu off
the main menu, and from there, the submenu Net Sysop Access, to
set up access for net sysops. This is also the menu where you set
access to your RoseMail Door, to prescans, and to your RoseNet
mail system.
If you wish, you can flag conferences for a user ahead of time.
If you do so, this will allow the user to download messages from
RoseMail on the first call without having to use the conference
selection menu, assuming the user has the appropriate security as
defined in PCBoard for the conferences you flag.
Flags 6, 7, and 8 are the flags with which you will be primarily
concerned in this submenu.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 151
Screen 17. Set conference flags by user account.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 2.00ßSystem Manager (01-26-93 17:00) │
│ Copyright (C) 1991-93 Rose Media Incorporated │
│ │
│ Set conference flags by user account │
│ User Name : JULIANNE FISCHER │
│ # Conference name 1 2 3 4 5 6 7 8 │
│ 0. Main Board Override prescan sec: N │
│ 1. HelpThyme User allowed in door: Y │
│ 2. NewsReadOnly User allowed RoseNet: Y │
│ 3. Pets │
│ 4. PSRMTSysops │
│ 5. ChatThyme │
│ 6. AsciiArt │
│ 7. AnsiArt │
│ 8. EMail │
│ 9. Direct-Mail │
│ │
│ CTRL-PgUp for previous user, CTRL-PgDn for next user, CTRL-F │
│ to find user. │
│ │
│ Press ESC (right mouse button) to return to net menu │
│ │
│ Deny netmail access in this conference. │
│ │
│ Use CTRL-J to jump to a conference, CTRL-S/CTRL-C to set/clear │
│ ranges. │
│ │
└────────────────────────────────────────────────────────────────┘
See the list of keys near the beginning of the main reference
section for descriptions of Ctrl-J, Ctrl-S, and Ctrl-C, which will
assist you in configuring this area.
Flag 1: Scan for personal messages
When a caller selects personal messages in RoseMail, this
flag is set. You can set the flag for the user if you wish.
If you set this flag, the caller's personal messages will be
delivered even if that caller has not selected the
conference.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 152
Flag 2: Scan for public messages
The caller can set this flag by selecting the conference in
RoseMail, assuming the caller has sufficient security and the
conference is public. You may set this flag for the caller
if you wish.
Flag 3: Flag not used
Flag 4: Flag not used
Flag 5: Flag not used
Flag 6: User gets SysOp status in this conference
All messages (including private) are accessible to the user.
Flag 7: Deny the user access to this conference
Flag 8: Deny netmail access in this conference
Three other fields in this screen are accessed by pressing your Up
arrow key. These fields determine user access to prescans, to
your RoseMail Door, and to your RoseNet mail system.
Override Prescan sec
Here, you may set up prescans for a caller whose security
normally does not allow prescans. To allow this, set this
field to YES.
User allowed in door
Here you determine the user's access to your RoseMail Door.
This field is set to Yes by default. If you need to shut a
user out of RoseMail, set this field to No.
User allowed RoseNet
This field is set to Yes by default. If you wish to shut a
user out of your RoseNet mail system, set this field to No.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 153
MODULES TO ADD INTO MESSAGE PACKETS: ADD-IN FILES
--------------------------------------------------
Add-In files are files that can be added to a mail packet
automatically based on their DOS file dates. That is, if a caller
selects files you provide as Add-In files, these are added to
their mail packets each time files of the same name have their DOS
file dates updated.
See the Caller's Guide to RoseMail for information on selecting
these files from within the RoseMail door, or resetting the
selections so that the files can be added to the mail packets even
if the caller has downloaded them before.
You may make any kind of DOS file available to your callers as
Add-In files. Because you can set the minimum security level
individually for each file you make available this way, you
maintain full control of who may select which file for download in
the mail packet.
Add-in files are similar to those provided by QMail's SERVICES.
To make a file available to your callers, you must include the
file itself, in compressed form, and also, you must include, in
the same directory, a "SERVICES" file. This SERVICES file is
compatible with Mark "Sparky" Herring's DeLuxe2 mail reader.
RoseReader users will need to make sure they have a permanent
\SERVICES directory properly configured in order to read these
files.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 154
Screen 14. Modules to add to message packets.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 1.70 System Manager (02-24-92 16:00) │
│ Copyright (C) 1991, 92 Rose Media Incorporated │
│ │
│ Modules to add into message packets │
│ │
│ Add-in name File name Security │
│ Newbytes C:\PCB\ROSE\ADDIN\TECH.ZIP 50 │
│ Invent C:\PCB\ROSE\ADDIN\INVENT.ZIP 50 │
│ Imagine C:\PCB\ROSE\ADDIN\IMAGINE.ZIP 50 │
│ 0 │
│ │
│ Press ESC (right mouse button) to return to main menu │
│ │
└────────────────────────────────────────────────────────────────┘
Add-in name
-----------
This is the name of the module that designates a file or files
that a caller can include in message packets when these added
files are enabled by the sysop.
If callers select Add-in files, by typing "ADD" at the RoseMail
Command prompt and selecting a file or files from the menu, these
modules will be added to their mail packets, assuming the DOS file
dates are later than the date that particular caller last
downloaded through RoseMail. Callers can also reset their Add-In
choices from within the RoseMail Door. See the Caller's Guide to
RoseMail for details.
File Name
---------
Here you fill in the entire drive, path, and <filename.ext> for
each Add-In file you provide. For each file you provide, you fill
in a separate line.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 155
Security
--------
Here you list the minimum security level required in order to
download the file listed on this line.
Add-In files and SERVICES FILES
-------------------------------
There are two steps to providing Add-In files for callers. First,
you archive the files, so that you have the files to be
distributed compressed, and placed into the \ADDIN directory we
suggested you create, as described earlier in this guide.
Next, for each Add-In file you place into your \ADDIN directory,
you create a SERVICES file. Each of these files is exactly the
same as every other SERVICES file except for its <filename>.
However, you need multiple copies of the SERVICES file, one for
each Add-In file you provide. The SERVICES file must have the
same name as the <filename> of the Add-In file, and it must have
NO EXTENSION name. You must place BOTH the compressed ADDIN[.ZIP]
file and the SERVICES file in your \ADDIN directory.
For example, if you create an Add-In file called INVENT.ZIP, you
must make a copy of your SERVICES file, and call it INVENT, and
both INVENT.ZIP and INVENT must be placed in your \ADDIN
directory. Similarly, if you create an IMAGINE.ZIP, you must copy
your SERVICES file to a file named IMAGINE, and make sure that
both IMAGINE.ZIP and IMAGINE are in your \ADDIN directory.
The SERVICES file
-----------------
Here is an example of the SERVICES file you keep around and make
copies of for EACH Add-In file you post for your callers. This
one is set up to use PKZIP. If you are using a different
compression/decompression method, substitute the appropriate
command for "@PKUNZIP@".
@echo off
cls
@PKUNZIP@ @SERVICE@ %S
%L %S\*.*
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 156
The easiest way to handle these files is to keep the file called
SERVICES in your \ADDIN directory, and each time you post a new
Add-In file, simply copy the SERVICES file to a new file that has
the same <filename> (no extension) as the new .ZIP file you are
posting for your callers.
For example, your \ADDIN directory might look something like this:
SERVICES
TECH.ZIP
TECH
INVENT.ZIP
INVENT
IMAGINE.ZIP
IMAGINE
where each of the filenames that has no extension represents an
exact copy of the file called SERVICES.
MAGAZINES
---------
These are periodical magazines and articles.
The caller can download and browse through these files; they are
magazine-like files, which may be updated from time to time.
When you add new magazines or periodicals, you need to enter them
in the Magazines screen to make them available to your callers.
If you are merely updating a magazine or periodical with the same
name, you do not need to reconfigure this area, since callers who
have selected Magazines will receive new versions of the same
magazine when the DOS file date is later than that of their last
downloads. In other words, the downloading of Magazines by
callers works in the same way as Add-In files.
The simulated screen here is filled out; your filling may be
different.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 157
Screen 15. Magazines and Periodicals.
┌────────────────────────────────────────────────────────────────┐
│ │
│ RoseMail 1.70 System Manager (02-24-92 16:00) │
│ Copyright (C) 1991, 92 Rose Media Incorporated │
│ │
│ Magazines and periodicals │
│ │
│ Magazine name File name Security │
│ Trivia C:\PCB\ROSE\MAG\TRIVIA 50 │
│ Reviews C:\PCB\ROSE\MAG\REVIEWS 50 │
│ USAToday C:\PCB\ROSE\MAG\USATODAY 50 │
│ 0 │
│ 0 │
│ 0 │
│ │
│ Press ESC (right mouse button) to return to main menu │
│ │
└────────────────────────────────────────────────────────────────┘
Magazine name
-------------
This is the name of the magazine or periodical to display to the
user.
File name
---------
This is the drive, path, and filename of the magazine file.
Security
--------
This is the minimum security level that the user needs to be able
to select the magazine.
NOTE: No SERVICES files are required for Magazines.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 158
CONFERENCE OPTIMIZE
-------------------
Here, when you press Enter with "Conference Optimize" highlighted,
you create or update the file called OPT.LST. This file speeds
caller selection of conferences. It also speeds up mail scans in
the RoseMail Door. OPT.LST is automatically saved in the
directory where your CNAMES.@@@ file is located. You must run
Conference Optimize every time you make changes to the
configuration of your PCBoard conferences using PCBSetup, to
update the information contained in OPT.LST, so that RoseMail will
recognize the changes. You also need to run Conference Optimize
when you upgrade your RoseMail from one version to another.
If you are running a multi-node system, and a caller is online
when you use Conference Optimize, it may take several attempts to
update OPT.LST, since the file is shared, and cannot be written to
while someone else is using it. It is easiest to run Conference
Optimize when PCBoard is not running.
EXIT
----
To exit and save your RMAIL.DAT (and CONFDATA.DAT) configuration
file(s), press ESC from the main menu of the RoseMail System
Manager. Answer "Y" to the question about saving your
configuration. To exit without saving a new version of RMAIL.DAT,
reply "N" to the question.
NOTES ON SAVING RMAIL.DAT INFORMATION
-------------------------------------
Some of the menu items in the RoseMail System Manager, such as
"Start RDX rebuild" (under Duplicate checks) and "Conference
Optimize," run routines that perform tasks apart from
configuration, and therefore do not affect your configuration
file, RMAIL.DAT. When you run these programs, you may exit the
RoseMail System Manager without saving your configuration.
In some submenus, information is saved to disk when you make a
change from that menu. You may be asked if you wish to save
information or not.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 159
The principle holds: "When in doubt, save your information." If
you are not sure exactly what information you are about to save,
you can select the submenu and examine what is there.
TIP: If you are not going to make a special
configuration for any node right now, you have
finished your current installation. You might test
your RoseMail to find out if there are any errors.
Particularly, it is a good idea to test your standard
configuration before making any special ones.
Naturally you will want to make some test mailruns as
well, to make sure your conference configuration is
set up correctly, and that your HUB.QWK and HUB.REP
packets are inserted correctly.
NOTE: If you have finished your configuration, this is a good
time to back up your installation. Run your favorite backup
program. Do not write over the backup you made just before you
started installing RoseMail.
SPECIAL CONFIGURATIONS FOR INDIVIDUAL NODES
-------------------------------------------
Wide beta note, Sat 6 Feb 1993, 18:25: There may be additions
coming to these instructions, concerning setting up different
conference areas on a special node. The operation will certainly
be somewhat tricky, because I believe separate CNAMES files will
be required for such an operation. Therefore, the section
RoseMail Operations, later in this guide, would contain such
information in summarized form.
(Wide beta:) Furthermore, information on setting up cross-echoed
conferences will be forthcoming.
9) You can configure any of your nodes with a special
configuration different from your standard one.
If you have followed the instructions in this guide, your
standard configuration is in the file RMAIL.DAT, which you
should find in your C:\PCB\ROSE directory (or equivalent),
along with the files RM.EXE and ROMAIL.EXE, and
ROSEMAIL.KEY if your RoseMail is registered.
To make a special configuration for any node, complete the
following steps:
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 160
9-A) Change to the node directory you are about to configure.
If you are not going to change everything, it is
probably easiest if you begin by copying RMAIL.DAT from
your C:\PCB\ROSE (or equivalent) directory to the node
directory you are going to configure. Also, copy your
ROSEMAIL.KEY file to this node directory if it is not
already present there.
9-B) Run RM.EXE (RoseMail System Manager) from this node
directory. For instance if you are making a special
configuration for Node 3, make sure you are logged onto
your node 3 directory, and, from the DOS prompt, type:
c:\pcb\rose\rm
9-B-1) Now, go through the RoseMail System Manager's menus,
and change anything that needs changing. Consult the
main reference section above if you need assistance.
When you exit and save your configuration, the
RMAIL.DAT in your specialized node directory (in this
instance, \PCB\NODE3) will be updated to reflect the
changes you made. You may then rename the RMAIL.DAT
so that its filename reflects the node it belongs to,
for instance: "RMAIL.3".
NOTE: Hereafter, you will need to make sure, when making any
configuration changes, that you are accessing the version of
RMAIL.DAT that you WISH to access. For instance, if you wish to
change something on Node 3, and that is a node you have configured
in a special way, make sure you log onto Node 3 and run RM.EXE
from there, or specify the RMAIL.3 file when you run RM.EXE.
You might, for example use one of the following command sequences
if changing something in the configuration for Node 3:
cd\pcb\node3
c:\pcb\rose\rm rmail.3
OR, if you have not renamed the RMAIL.DAT file for Node 3:
cd\pcb\node3
c:\pcb\rose\rm rmail.dat
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 161
OR, if you do NOT change directories to the Node 3 subdirectory,
you can use a command line like this:
c:\pcb\rose\rm c:\pcb\node3\rmail.dat
Or, if you have renamed the RMAIL.??? file for Node 3:
c:\pcb\rose\rm c:\pcb\node3\rmail.3
Notice, though, that you do not have to rename the RMAIL.DAT file
if it is more convenient for you to leave it named RMAIL.DAT
regardless of the node it belongs to. You can leave the file in
the node directory, and make sure you access the correct RMAIL.DAT
file by logging onto the node directory before you start RM.EXE,
thus:
cd\pcb\node3
c:\pcb\rose\rm rmail.dat
Or you can be even more specific, and avoid logging onto the node
directory, thus:
c:\pcb\rose\rm c:\pcb\node3\rmail.dat
9-C) Edit the ROSEMAIL (DOOR, or "keyword") file, and include
a branch so that when the special node is accessed, the
correct RMAIL.DAT file will be used. See the Guided
Tour at the beginning of this guide for an explanation
of why this branching is necessary.
9-C-1) Use your text editor to edit the ROSEMAIL (DOOR.BAT)
file, which you will find in C:\PCB\ROSE (or its
equivalent). Notice that you will now need to use a
variable to cause a branch transfer to access the
desired node when DOOR.BAT is run (see the Guided Tour
at the beginning of this guide if you have now read so
much that you are lost). The most convenient type of
variable to use for this purpose is a DOS environment
variable that provides the digits of the node number
that you are configuring. There are a couple of
different ways that you can make sure that the
required variable is set before a caller opens your
RoseMail Door.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 162
9-C-1-a) If you are running PCBoard 14.5a, and have not
used the /NOENV switch described in the PCBoard
14.5a manual, you can use the DOS environment
variable PCBNODE, which will be set automatically
at the time a caller starts RoseMail.
9-C-1-b) If you are running PCBoard 14.5 (you have not
upgraded to version 14.5a), you can set the
variable PCBNODE (or some similar variable of
your choosing) in the BOARD.BAT or AUTOEXEC.BAT
file(s) for each node for which you make a
special configuration. Make a note to set this
variable for each node you configure in a special
way in your BOARD.BAT or AUTOEXEC.BAT for that
node. You would use a DOS command such as: "SET
PCBNODE=nn", where "nn" is the number of the
node, represented in digits.
9-C-1-c) Add the necessary branch(es) to your ROSEMAIL
(keyword) file. If your special configuration is
for Node 3, your ROSEMAIL file might look
something like this when you have finished:
If %PCBNODE%==3 goto NODE3
C:\PCB\ROSE\ROMAIL
BOARD
:NODE3
C:\PCB\ROSE\ROMAIL C:\PCB\NODE3\RMAIL.3
BOARD
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 163
You can see that when a caller starts RoseMail
from Node 3, DOOR.BAT will cause a branch to the
correct ROMAIL command line for Node 3. This is
because the PCBNODE variable will have been set
to 3 by your AUTOEXEC.BAT or by your BOARD.BAT,
or by PCB145, if you are running version 14.5a
and you have not used the /NOENV switch. As
illustrated in the example just above, DOOR.BAT
branches to the label NODE3, accessing the
special RMAIL.DAT file RMAIL.3, which you have
stored in the Node 3 directory. However, if a
caller opens RoseMail from a node with a standard
configuration, the BOARD instruction immediately
following the standard ROMAIL command line will
cause DOOR.BAT to terminate. See the Guided Tour
at the beginning of this guide for any further
explanation you need.
Here is an example of a ROSEMAIL file that
contains branches for two different nodes each
configured in a special way, while the other
nodes all access the common, shared,
configuration file (RMAIL.DAT) that lives in the
\PCB\ROSE directory.
If %PCBNODE%==21 goto NODE21
C:\PCB\ROSE\ROMAIL
If %PCBNODE%==22 goto NODE22
C:\PCB\ROSE\ROMAIL
BOARD
:NODE21
C:\PCB\ROSE\ROMAIL C:\PCB\NODE21\RMAIL.21
BOARD
:NODE22
C:\PCB\ROSE\ROMAIL C:\PCB\NODE22\RMAIL.22
BOARD
9-C-2) There is one element that you may want to check if you
have been running an earlier version of RoseMail, and
you have upgraded to version 1.70. If you have used
the #-variable or the PCBNODE variable in the File
Paths location for PCBOARD.SYS, you will need to use
the /n switch on the command line in the ROSEMAIL file
that starts ROMAIL.EXE.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 164
9-C-2-a) The /n switch is merely a switch at the end of
the command line that identifies the node number.
If you have used a variable in the File Path
location for PCBOARD.SYS, add "/<node number>" to
the end of the command line for the node
concerned.
For instance, your Node 3 branch in the ROSEMAIL
file should look something like this:
:NODE3
C:\PCB\ROSE\ROMAIL C:\PCB\NODE3\RMAIL.3 /3
BOARD
Make sure you have a space between "ROMAIL" and
"RMAIL.3" and another one between "RMAIL.DAT" and
"/3".
9-C-3) Save your new ROSEMAIL file and exit your editor.
That is all. Now you may test your RoseMail.
9-C-4) Repeat all the steps in this section ("Special
configurations for individual nodes") for any other
nodes that require special configurations. Make sure
that your global ROSEMAIL (keyword) file contains a
branch for each node that you configure in a special
way.
ROSEMAIL OPERATIONS
-------------------
Wide beta note, Sat 6 Feb 1993, 18:28: This section will be
expanded during the next few weeks. Please send your suggestions
for what you would like to have covered here. There is no
guarantee that there will be room for all your suggestions, but we
will try to include the most commonly useful operations.
There are a number of different tasks you may occasionally want or
need to perform. This section describes a few of them, and deals
also with special considerations you may need to attend to in
performing some regular tasks.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 165
Sysop Local Hotkeys
-------------------
If you are monitoring a caller's session, you will find
certain keys helpful. These keys are mostly the same as the
PCBoard keys. Where they differ, that is noted.
Table 3: Sysop Local Hotkeys
-----------------------------
F3 - Toggle printer (places P on status line)
F4 - Toggle Page Bell (places B on status line)
F5 - Shell to DOS
F7 - Caller Alarm (places A on status line)
F8 - Return to BBS (In PCBoard, this logs the
caller off)
F9 - Toggle screen on/off
F10 - Sysop Chat Mode (engage caller in Chat)
ESC - End Sysop Chat Mode (return caller to previous
activity)
ALT-N - Toggle sysop next (Flashing N appears on
status line)
ALT-X - Toggle exit to DOS after caller (Flashing X
appears on status line)
Notes:
1. Flags appear in the order (PAB). when the option is
set ON. Flags that you have disabled will not
appear. If all flags are disabled, nothing
appears.
2. The last two flags, Alt-N and Alt-X, will not
appear if you are using the PCBoard /LOCALON
switch. If you wish to see the last two flags
mentioned, use a BOARD.BAT that omits the /LOCALON
switch, and select local user logon from the Call-
Waiting screen.
If your PCBOARD.DAT specifies a modem for this node,
your modem must be live when you log on, or you may
hang the modem or your system.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 166
3. P (F3, Toggle Printer) and A (F7, Alarm) do nothing
in RoseMail; they do, however, set the status for
PCBoard, so that they will take effect when the
caller returns to PCBoard.
Pre-scan QWK packets for net sysops
-----------------------------------
If net sysops are collecting mail from you, you can pre-scan
.QWK packets for them. You make up the packets at your
convenience, perhaps during your event. When the caller logs
on and starts RoseMail, RoseMail immediately indicates the
mail packet is waiting, and sends the packet already scanned.
The first attempt to download when an offline packet already
exists for the caller will send the pre-existing packet,
without the need for a new download scan and compression.
There are two methods available for pre-scanning packets.
Method A is the easiest, and it operates faster than
Method B. For all practical purposes, you will want to use
Method A, but you can fall back on Method B for whatever
reason appears necessary to you.
IMPORTANT NOTE: You may have the board up or down while doing
prescans. However, NEVER attempt to pack your USERS files during
a prescan of any kind.
ROMAIL keeps a file called PRESCAN.LOG in the directory you choose
to be your offline netmail directory. This file shows for whom
you are doing prescans.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 167
Prescan Method A: "ROMAIL /P" prescan
--------------------------------------
This is the easiest method to use for prescanning mail packets for
callers. You can use a batch file to call ROMAIL without calling
PCB145.EXE first.
Before setting up your batch file, you will want to check your
Prescan Security level in the RoseMail System Manager (RM.EXE),
under the Options menu, Prescan security. Once you have set this
level, callers may choose Option 11 in your RoseMail Door to
enable prescans for themselves, assuming their security level is
sufficient. Notice that as explained below, you may perform
prescans for users who do not have a sufficient security level.
For the prescan to work, however, the caller must have set Option
11 to Yes.
A valid RMAIL.DAT file must be available to ROMAIL when it is run,
so you will need to log onto the node directory from where you
perform the prescan, or specify a valid RMAIL.DAT file on the
ROMAIL command line. Also, you will need a valid PCBOARD.DAT file
in the current directory, so the easiest way to use the
"ROMAIL /P" method is to log onto the node directory first.
If you prefer, you may specify the RMAIL.DAT file on the ROMAIL
command line, thus:
c:
cd\pcb\node3
c:\pcb\rose\romail rmail.3 /P
If you are running a single-node system, and your node directory
is the same as your \PCB directory, you might use commands like
this, because your PCBOARD.DAT file is probably in C:\PCB, and
your RMAIL.DAT file is in C:\PCB\ROSE:
c:
cd\pcb
c:\pcb\rose\romail c:\pcb\rose\rmail.dat /P
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 168
Prescan Command Line Options (ROMAIL /P method)
-----------------------------------------------
If you wish to set options for this command, add them as switches
at the end of your ROMAIL command line, thus:
c:\pcb\rose\romail c:\pcb\node21\rmail.21 /p <prescan options>
The options available are as follows.
For the <sec>, <low> and <high> in the examples below, substitute
the digits of the appropriate security levels. Security levels
that you set with these switches will override the minimum
security level you set under Options in the RoseMail System
Manager (RM.EXE).
/S=<sec> - only prescan packets for callers with the
given security level <sec>.
/S=<low>+ - only prescan packets for callers with
security greater than or equal to the
given level.
/S=<high>- - only prescan packets for callers with
security less than or equal to the given
level.
/S=<low>-<high> - only prescan packets for callers within
the given range of security levels.
"/N=<first last>" - scan mail packet for one specific user.
Make sure to include the quote marks as
shown.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 169
You can perform prescans for specified callers by naming the
caller for whom you are prescanning. You can also make a list of
callers for whom you wish to prescan mail packets, and save the
list to a text file, and then specify the text file on the ROMAIL
command line.
/N=<username> - scan mail packet for one specific user,
where the UserID consists of a single
name.
/L=<filename.ext> - scan all users listed (one per line,
flush left, do NOT use quote marks) in
the text file specified.
You may add /S switches as shown above to the /N or /L switches,
and they will work as long as the specified callers have selected
the Prescan Option (Option 11 in the RoseMail Door).
A few examples should clarify these combinations for you. Suppose
you have a text file listing of callers for whom you wish to
prescan mail packets:
vic kass
drew miller
a.nonny mouse
corazon twinkletoes
Let us assume that your minimum security level for prescanning is
set to 255 (which would, in effect, disable prescans for everyone)
under Options in the RoseMail System Manager. The callers on your
list have all set Option 11 to Yes in your RoseMail Door, and they
all share a security level of 80.
Now you can use a batch file to prescan mail packets for all the
users on the list illustrated just above. This list,
SCANLIST.TXT, is located in your Node 21 directory, and you will
perform the scan from there. The minimum security level of 255
that you set in RM.EXE is overridden by the command line.
c:
cd\pcb\node21
c:\pcb\rose\romail rmail.21 /L=scanlist.txt /s=80
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 170
Prescan Method B: TPA prescan with batch file
---------------------------------------------
You can prescan packets for your callers from a batch file that
uses the TPA, or "Third Party Application" method, where you
begin and end by calling PCB145.EXE. Callers for whom you
prescan using this method must have set Option 11 to Yes in
your RoseMail Door, and their security levels must be
sufficient for the prescan. PCBoard returns you to DOS when
the prescan is finished.
For each net sysop for whom you are pre-scanning .QWK
packets, your batch file should contain the following three
lines (but omit the line numbers, which are indicated here
merely to identify the lines for later comment).
Notice that this method requires considerable setup and
maintenance on your part.
Before you attempt a prescan with this method, make sure that
you have a valid RMAIL.DAT file in the node directory from
which you perform the prescan.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 171
Table 4: TPA method, Batch File To Pre-scan QWK Packets
--------------------------------------------------------
For simplicity's sake, we illustrate first with the basic batch
file, containing no drive letters or pathnames. The batch file is
reproduced later, showing examples of drive and pathnames. Since
your PCBOARD.DAT file will be accessed during this procedure, you
will need to log onto one of your node directories, or, if you are
running only a single node, log onto your node directory, whether
it be something like \PCB or \PCB\NODE1, before running the batch
file. Or your batch file may, of course, log onto the node
directory itself.
1. PCB145 /USERSYS;First;Last;PWRD:<user's password>;TPA:ROSEMAIL
2. ROMAIL ;D;Y;G
3. PCB145
(where "First" and "Last" represent the user's logon name)
Line 1 - will create a USERS.SYS file for the user named
Line 2 - (with the leading semicolon) will perform the offline
scan.
If a QWK packet already exists for the user, it will
be appended to.
Line 3 - will copy the user's message pointers from USERS.SYS
back to the user files.
NOTE: PCBoard will exit to DOS after executing this
last command.
When you perform a prescan, you may notice the following:
When the packet is complete, you see an indication "900
minutes used." This is nothing to worry about. The pre-
scan simply makes sure it has enough time to operate in.
The user is not docked of any time.
Notice the leading semicolon before the D in the ";D;Y;G"
command. If you forget to include the leading semicolon,
the prescan will not work.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 172
You can include the pre-scan in your event. Make sure you
include these three lines for each net sysop who calls you,
and that you edit the first line appropriately for each
sysop.
Illustrating now with an example that shows changing directories
to a node directory, and calling PCBoard from the \PCB directory:
c:
cd\pcb\node21
c:\pcb\PCB145 /USERSYS;First;Last;PWRD:<password>;TPA:ROSEMAIL
c:\pcb\rose\ROMAIL ;D;Y;G
c:\pcb\PCB145
You can make multiple copies of this generic example, and
substitute your drive and pathnames, and the user information
(firstname, lastname and userpassword) as needed. For each
prescan you perform, one per user, you must include the last three
lines of the four shown above, with that user's information filled
in.
The flexibility of this TPA method lies in the ROMAIL command
line, where you can use other commands besides the ";D;Y;G".
Lock a user out of RoseMail (or restore access to a user)
---------------------------------------------------------
All registered users are listed under the User Flags menu of the
RoseMail System Manager (RM.EXE).
If for any reason you need to deny a user access to your RoseMail
Door, or to RoseNet mail, or to restore access after a lockout,
you can do so by completing the following steps.
1) Run RM.EXE (the RoseMail System Manager).
2) Select User Flags from the main menu.
3) Press Ctrl-F and enter the user's full name.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 173
4) Press your Up Arrow to reach the field "User Allowed in
Door" (or User allowed RoseNet).
4-A) To lock a user out: type "N" into the field.
4-B) To restore a user's access: type "Y" into the
field.
5) Press ESC to leave the field.
6) Type "Y" to save the new information.
7) Press ESC to exit the RoseMail System Manager.
8) Type "N" to avoid updating RMAIL.DAT, since the
information is saved in USERS.INF, not in RMAIL.DAT.
Settings to use if your hub has RoseMail
----------------------------------------
If the hub you call uses RoseMail, please see the Caller's Guide
to RoseMail for information on how to use RoseMail as a caller or
as a net sysop.
The entire Caller's Guide to RoseMail applies to you as a caller.
However, there is one setting, Option 12, under Options in the
RoseMail Door that you as a sysop should treat in a way different
from that used by callers who are not sysops, and there are a
couple of other RoseMail Door Option settings that you may wish to
consider.
Option 12 in the RoseMail Door, Download Your Replies, allows
callers to check on the replies they posted by including them in
their QWK packets. However, If you, the sysop, download replies
you wrote on your board, you may find that they insert on your
BBS, duplicating the messages you wrote online or using RoseReader
for Sysops.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 174
Option 13 in the RoseMail Door, Use Current Date/Time, can be set
by a caller to allow an uploaded message to take on the BBS system
date/time at the time of upload. You, the sysop, can use
Conference Flag 15 in the RoseMail System Manager (RM.EXE) to
control this setting individually for each conference. If you
have set this flag for a particular conference, but the caller has
not selected Option 13, your setting will override the caller's
choice.
Another setting, Option 20, Do Not Send NDX Files, allows you, the
sysop, to reduce your packet size slightly, saving you some
download time. Callers who are not downloading netmail packets
will normally wish to include the NDX files in their packets.
Although RoseReader will generate missing NDX files, not all mail
readers may do this.
Option 12: Download your replies
---------------------------------
You should set this option to NO on any board where you
are sending echo mail, to prevent downloading messages you
entered and having them inserted again on your board. The
addition of the tagline from your board allows the
messages to get past RoseMail's check for duplicates,
since you are not normally expected to download the
messages you just uploaded. So, what is a convenience for
callers could be a nuisance for net sysops.
Option 13: Use current date/time
---------------------------------
Sysops who scan mail from their boards and send it to the
hub for distribution should normally set this option to NO
on the hub, as a courtesy to their callers, so that
callers' messages do not get stamped at the hub with the
hub's date and time.
Some callers habitually include the date and time of
writing in the body of the message. Should this habit
become widespread, using the date and time of posting on
the hub would be a convenient tracking method for sysops,
should messages go astray. Quite possibly callers would
also find it convenient, or at least not object to this
arrangement.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 175
Note that on your own board, you can force this Option to
be set to YES for all callers in a particular conference
by setting Conference Flag 15 for that conference.
Option 20: Do not send NDX files
---------------------------------
The option to exclude .NDX files from your mail packet is
primarily for sysops. If you are not reading your netmail
packets with an offline reader, you may set this option to
YES to exclude the .NDX files your packets.
If, however, you are taking conferences from your hub that
you do not yourself carry on your own BBS, you will
probably want to leave this option set to NO, so that you
can read and reply to mail with your offline mail reader.
COMMAND SUMMARY
---------------
Wide beta note, Sat 6 Feb 1993, 18:37: The new conference
selection command to select messages addressed to You and to ALL
will be covered in later versions of this document. Other new
commands for RoseMail 2.00 may also be added during the next few
weeks.
Conventions in Text
-------------------
In the following text, square brackets [] indicate that the
addition to the command line is optional. Angle brackets <>
indicate the entity or unit that is to be included on the
command line.
What to do with command lines
-----------------------------
You can include most of the following command lines in your
event, including the command lines illustrated below for
ROMAIL.EXE that pre-scan .QWK packets for net sysops. Apart
from the prescanning ROMAIL command lines, you cannot run
ROMAIL.EXE in your event.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 176
ROMAIL.EXE
----------
You do not normally run ROMAIL.EXE yourself. This program
runs when your caller opens the RoseMail Door. When your
caller opens the door, ROMAIL.EXE is called from the PCBoard
DOOR.BAT file - the file called ROSEMAIL in this guide.
However, you do run ROMAIL.EXE if you are pre-scanning .QWK
packets for net sysops, and you may place this command in
your event. See "Pre-scan QWK packets for net sysops",
above, for details.
The ROSEMAIL (DOOR.BAT) file command line
-----------------------------------------
ROMAIL [<RMAIL.DAT>] [/<node number>]
You include "RMAIL.DAT" for nodes where you have a
special configuration, and therefore, an RMAIL.DAT in
the current (node) directory. See the section entitled
"Special configurations for individual nodes," above,
for details.
You need to include the node number switch ("/n", where
"n" is the node number) when you have used the #-
variable or the PCBNODE variable ("%PCBNODE%") in the
File Paths configuration for PCBOARD.SYS.
Using the /n switch on a ROMAIL command line limits that
command line to the node represented by the switch, so
in a global configuration, where you are using a single
RMAIL.DAT file for several nodes, you will avoid using
"#" or "%PCBNODE%" in the File Paths location for
PCBOARD.SYS. But where you have configured one or more
nodes with special configurations, because each node
configured in a special way has its own RMAIL.DAT (or
RMAIL.<node_number>) file, you may use "#" or
"%PCBNODE%" in the location for PCBOARD.SYS if you wish,
and the required /n switch will then not be a nuisance.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 177
Pre-scan for QWK packets
------------------------
When you pre-scan for QWK packets, you must include a
leading semicolon before the RoseMail command letters,
thus:
ROMAIL ;D;Y;G
Notice the semicolon before the "D" in the command
line. This indicates that you are running from the DOS
command line, instead of being online to the board.
PCBoard will exit to DOS after this command line is
executed. You call PCB145.EXE directly for this type
of command.
Here is a full summary of command lines in which ROMAIL is
used to prescan QWK packets for your callers.
ROMAIL /P method
----------------
For the <sec>, <low> and <high> in the examples below, substitute
the digits of the appropriate security levels. Security levels
that you set with these switches will override the minimum
security level you set under Options in the RoseMail System
Manager (RM.EXE).
/S=<sec> - only prescan packets for callers with the
given security level <sec>.
/S=<low>+ - only prescan packets for callers with
security greater than or equal to the
given level.
/S=<high>- - only prescan packets for callers with
security less than or equal to the given
level.
/S=<low>-<high> - only prescan packets for callers within
the given range of security levels.
"/N=<first last>" - scan mail packet for one specific user.
Make sure to include the quote marks as
shown.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 178
You can perform prescans for specified callers by naming the
caller for whom you are prescanning. You can also make a list of
callers for whom you wish to prescan mail packets, and save the
list to a text file, and then specify the text file on the ROMAIL
command line.
/N=<username> - scan mail packet for one specific user,
where the UserID consists of a single
name.
/L=<filename.ext> - scan all users listed (one per line,
flush left, do NOT use quote marks) in
the text file specified.
You may add /S switches as shown above to the /N or /L switches,
and they will work as long as the specified callers have selected
the Prescan Option (Option 11 in the RoseMail Door).
PCBoard with TPA method
-----------------------
PCB145 /USERSYS;First;Last;PWRD:<user's password>;TPA:ROSEMAIL
ROMAIL ;D;Y;G
PCB145
(where "First" and "Last" represent the user's logon name)
Line 1 - will create a USERS.SYS file for the user named
Line 2 - (with the leading semicolon) will perform the offline
scan.
If a QWK packet already exists for the user, it will
be appended to.
Line 3 - will copy the user's message pointers from USERS.SYS
back to the user files.
NOTE: PCBoard will exit to DOS after executing this
last command.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 179
RM.EXE
------
RM.EXE performs several tasks besides serving as your System
Manager. Its command lines are as follows:
RM.EXE <no parameters>
Used this way, this command loads the RoseMail System
Manager to configure your system, to maintain your system,
or to configure user information.
RM.EXE <HUB> /S
Scan messages from your board to create a HUB.REP file,
where <HUB> is the mail packet name of your hub.
RM.EXE <HUB> /I
Insert messages from a HUB.QWK file, where <HUB> is the
mail packet name of your hub.
RM.EXE RDX:<low>-<high>
(where <low> is the lowest conference number to include,
and <high> is the highest)
This command rebuilds .RDX files for the range of
conferences specified with <low> and <high>.
IN CASE OF DIFFICULTY
---------------------
ESCaping unwanted changes
-------------------------
Use Ctrl-U (Undo) to back out of small changes
----------------------------------------------
When configuring with the RoseMail System Manager, before you
take the drastic step of abandoning your new RoseMail
configuration entirely, be aware that as long as you have not
moved your cursor off the line or the field you are
configuring, you can restore the information contained there
previously by pressing Ctrl-U (Undo).
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 180
Use ESC to back out of all changes
----------------------------------
If, while you are configuring RoseMail, you decide you really
do not want to change anything after all, or if you want to
start all over again, you can ESCape without saving anything.
To do this, simply press ESC until you are asked if you want to
save your configuration. Then answer "N" (No) to the question
about saving the new configuration, and when you press <Enter>,
all will be left as it was before you started.
Finding RMAIL.DAT
-----------------
When you start the RoseMail System Manager (RM.EXE) for the first
time, you do not have a configuration file called RMAIL.DAT. If
you have run RM.EXE at all, even if you have NOT saved your
configuration, you do have a file called RMAIL.DAT.
If RM.EXE (the RoseMail System Manager) cannot find your RMAIL.DAT
file, it will make one for you. This is fine if you have never
saved RoseMail configuration information before. You can just
start out and configure as you like.
However, if you have already entered some information using the
RoseMail System Manager, you do have an RMAIL.DAT file that
contains that information. If RM.EXE cannot find that file, it
will make a new one in the current directory, and this occurrence
could be very confusing to you.
So, if you know you have run RM.EXE before, and you find that the
information you thought you saved previously is not included, you
should exit to DOS and find out just where the RMAIL.DAT file you
wish to work with is located. When you find it, log onto that
directory, and run RM.EXE from that directory, for instance, by
typing "c:\pcb\rose\rm" (without the quotes) at the DOS prompt.
The point is that if you already have an RMAIL.DAT file, it
contains a configuration of some kind, and you do not want to
write over that configuration by mistake - only by your design.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 181
UPGRADING your ROSEMAIL
-----------------------
To change from an unregistered to a registered version
------------------------------------------------------
If you have been running an unregistered version of RoseMail, and
you register your RoseMail and obtain a ROSEMAIL.KEY file, then
copy your ROSEMAIL.KEY file to each subdirectory where you have an
RMAIL.DAT file.
For instance, if you have multiple nodes, you will need to copy
your ROSEMAIL.KEY file to each node directory you have configured
with a special RMAIL.DAT file.
Now you will need to run RM.EXE from each subdirectory in turn
where you have RMAIL.DAT and ROSEMAIL.KEY files.
You might start in your main \PCB\ROSE directory; that is, log
onto C:\PCB\ROSE, and enter "RM" at the DOS prompt. A message
that says something like "RMAIL.DAT was incorrect... the problem
has been corrected" will flash by on your screen.
If you are not going to configure the Networks/NetMail information
now, you should perform the Conference Optimize. If you have an
established message base, you should rebuild your RDX files using
the Duplicate Checks menu. Also, read the SETUP.nnn instructions,
where "nnn" is the version number of your RoseMail, and follow any
instructions contained there. Then you may Exit and Save the
configuration. Otherwise, configure the Networks/NetMail
information (see the instructions in the main reference section),
and then exit and save the configuration.
Now run RM.EXE from each node directory in turn where you have
RMAIL.DAT files, making sure you are logged onto the correct
directory, and calling RM.EXE with the full pathname (for
instance, log onto your node 3 directory, and call RM this way:
"c:\pcb\rose\rm"). Perform your Conference Optimize, and your RDX
rebuild, and then exit and save your configuration.
When you have done this for each RMAIL.DAT file, your RoseMail has
acknowledged your registration. You may configure the
Networks/NetMail information at your leisure, if a sysop can ever
be said to have any of that rare commodity.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 182
From one minor version to another (e.g. from 1.60 to 1.70)
----------------------------------------------------------
Back up your system. Read the instructions that come with the new
.ZIP files, and follow them. Before you have finished the new
installation, you will need to save your new configuration as you
exit RM.EXE (The RoseMail System Manager).
You will remember that normally, if you exit the RoseMail System
Manager without saving your new configuration, your RMAIL.DAT will
remain unchanged. During upgrades, the situation is different.
RoseMail upgrades come with conversion programs that you do not
see. These programs sometimes alter files when you start the
RoseMail System Manager. RoseMail ALWAYS tells you if it is
making changes to files during an upgrade. Regardless, it is a
good idea, before you begin to install an upgrade, to make a copy
of your RMAIL.DAT file in a separate location.
Usually the three steps you will need to take when you make a
minor upgrade, such as from 2.00 to 2.01 are these:
(1) Back up your system
(2) Look for any instructions that came with your upgrade,
such as WHATSNEW.201 and SETUP.201
(3) Copy the new files over the old files
(4) Run RM.EXE (The RoseMail System Manager)
(a) Run Conference Optimize
(b) Under Duplicate Checking, Rebuild the RDX files
(c) Examine all the menus to determine that your
settings are correct, and if any additional
settings are present, set those as desired.
(d) Exit and save your new configuration.
NOTE! If you have more than one RMAIL.DAT (RMAIL.<node number>)
file, you need to run RM.EXE on EACH of those files to complete
your upgrade.
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 183
ENVOI
-----
May you and your callers enjoy RoseMail. Please join us in the
Rose or the RoseMail conference on U'NI-net, Smartnet or Intelec,
if you would like to make suggestions or comments or ask
questions. Thank you.
<END SYSOP'S GUIDE TO ROSEMAIL>
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 184
INDEX
"#-variable" . . . . . . . . . . . . . . . . . . . . . . . . . .18
/n switch. . . . . . . . . . . . . . . . . . .12, 81, 82, 164, 176
%1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91, 92
%2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91, 92
%3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91, 92
%4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91, 92
%5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91, 92
#-variable . . . . . . . . . . . . . . . . . .12, 80, 81, 163, 176
substitions for, in File Paths . . . . . . . . . . . . . . . .81
80286. . . . . . . . . . . . . . . . . . . . . . . . . . . . 4, 50
8086 . . . . . . . . . . . . . . . . . . . . . . . . 4, 30, 50, 51
8088 . . . . . . . . . . . . . . . . . . . . . . . . 4, 30, 50, 51
Add-In files . . . . . . . . . . . . . . . . . . . 29, 47, 69, 153
Add-In files and SERVICES FILES. . . . . . . . . . . . . . . . 155
Add/Update Third Party Application . . . . . . . . . . . . .31, 52
Address
Available Networks . . . . . . . . . . . . . . . . . . . . . .39
Alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
ALT-N. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
ALT-X. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Alternatives for installing DSZ. . . . . . . . . . . . . . .48, 49
ANSI Editor. . . . . . . . . . . . . . . . . . . . . . . . . . .72
edit ANSI help files . . . . . . . . . . . . . . . . . . . . .35
Archiving programs . . . . . . . . . . . . . . . . . . . . . . .84
Arranging to carry netmail . . . . . . . . . . . . . . . . . . 121
Arrow keys . . . . . . . . . . . . . . . . . . . . . . .60, 61, 66
ASCII Editor . . . . . . . . . . . . . . . . . . . . . . . . . .71
Attached files . . . . . . . . . . . . . . . . . . . . . . . . .21
Audit trail. . . . . . . . . . . . . . . . . . . . . . . . . . .21
AUTOEXEC.BAT . . . . . . . . . . . . . . . . . . . . . .48, 49, 98
Available Networks . . . . . . . . . . . . . . . 39, 125, 127, 128
Network name . . . . . . . . . . . . . . . . . . . . . . . . 129
Network number . . . . . . . . . . . . . . . . . . . . . . . 128
Pre-defined nets . . . . . . . . . . . . . . . . . . . . . . 130
Backspace key. . . . . . . . . . . . . . . . . . . . . . . . . .60
Batch file . . . . . . . . . . . . . . . . . . . . . . . . . . 170
BBS phone number . . . . . . . . . . . . . . . . . . . . . . . 103
BBS.Q99. . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
BBS.QW0. . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
BBS.QW1. . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
BBS.QWK. . . . . . . . . . . . . . . . . . . . . . . . . . 44, 103
BBS.REP. . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Bi-directional protocols . . . . . . . . . . . . . . . . . . . .91
Board Information. . . . . . . . . . . . . . . . . . . . . . . 103
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 185
Board name . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Board telephone number . . . . . . . . . . . . . . . . . .104, 105
BOARD.BAT. . . . . . . . . . . . . . . . . . . . . 48, 49, 98, 165
Bounced messages . . . . . . . . . . . . . . . . . . . . . . . .22
BRDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .50
BUFFERS= . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
Bulletin board name. . . . . . . . . . . . . . . . . . . . . . 103
Bulletins. . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Call-Waiting screen. . . . . . . . . . . . . . . . . . . . . . 165
Caller Alarm . . . . . . . . . . . . . . . . . . . . . . . . . 165
Caller Repeat Downloads. . . . . . . . . . . . . . . . . . . . 103
Caller's Guide to RoseMail . . . . . . . . . . . . .1, 3, 102, 173
Carbon copies. . . . . . . . . . . . . . . . . . . . . . . . . 116
Change from an unregistered to a registered version. . . . . . 181
Characters per second. . . . . . . . . . . . . . . . . . . . . 101
Chat Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Check the DSZ command lines. . . . . . . . . . . . . . . . . . .97
Checking a global RoseMail installation. . . . . . . . . . . . .41
CHECKLIST FOR CONFIGURING EXTERNAL TRANSFER PROTOCOLS. . . . . .95
Choose to set your pointers Before or After. . . . . . . . . . 143
Clark Development Company. . . . . . . . . . . . . . . . . . . . 4
Clear flags for a range of conferences . . . . . . . . . . . . .64
Clear multiple flags . . . . . . . . . . . . . . . . . . . . . .63
CNAMES.@@@ . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Co-sysops. . . . . . . . . . . . . . . . . . . . . . . . . . . .40
COM extension. . . . . . . . . . . . . . . . . . . . . . . . . .97
Com port in use. . . . . . . . . . . . . . . . . . . . . . . . .91
COMMAND SUMMARY. . . . . . . . . . . . . . . . . . . . . . . . 175
Compression program. . . . . . . . . . . . . . . . . . . . . . .37
Compression Programs . . . . . . . . . . . . . . . . . . . .67, 84
command lines. . . . . . . . . . . . . . . . . . . . . . .84, 86
Compression program. . . . . . . . . . . . . . . . . . . . . .85
Decompression program. . . . . . . . . . . . . . . . . . . . .86
executable filename. . . . . . . . . . . . . . . . . . . .85, 86
ID . . . . . . . . . . . . . . . . . . . . . . . . . . . .84, 85
Letter . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
pre-defined. . . . . . . . . . . . . . . . . . . . . . . . . .84
Compression: different versions of the same program. . . . . . .87
CompuServe . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Computer-to-modem speed. . . . . . . . . . . . . . . . . . .91, 92
CONFDATA.DAT . . . . . . . . . . . . . . . . . . . . . . . . . .73
Conference
maximum number of messages . . . . . . . . . . . . . . . . . 101
Conference data. . . . . . . . . . . . . . . . . .40, 68, 145, 146
Conference Flags . . . . . . . . . . . . . . . . . 40, 63, 68, 147
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 186
Allow aliases. . . . . . . . . . . . . . . . . . . . . . . . 149
Allow personal echo mail . . . . . . . . . . . . . . . . . . 147
Deny all insertion attempts. . . . . . . . . . . . . . . . . 147
Force conference to be scanned . . . . . . . . . . . . . . . 147
Force echo flag on . . . . . . . . . . . . . . . . . . . . . 149
Force message date/time to time of insertion.. . . . . . . . 149
Force the NEWS file. . . . . . . . . . . . . . . . . . . . . 148
Ignore PCBoard private flag. . . . . . . . . . . . . . . . . 149
Include download file listings . . . . . . . . . . . . . . . 148
Include new bulletins. . . . . . . . . . . . . . . . . . . . 147
Include the NEWS file. . . . . . . . . . . . . . . . . . . . 148
Include upload file listings . . . . . . . . . . . . . . . . 148
Insert all messages as personal. . . . . . . . . . . . . . . 147
Insert all messages as public. . . . . . . . . . . . . . . . 147
Conference number
jump to conference number (flag-setting keys). . . . . . . . .64
Conference Optimize. . . . . . . . . . . . . . . .40, 69, 158, 181
Conference Ownership . . . . . . . . . . . . . . . . .63, 125, 134
CONFIG.SYS . . . . . . . . . . . . . . . . . . . . . . .28, 45, 46
Configurable items . . . . . . . . . . . . . . . . . . . . 44, 103
Configuration
save, DOORS file . . . . . . . . . . . . . . . . . . . . . . .56
save, Networks/NetMail . . . . . . . . . . . . . . . . . . . .40
save, PCBSetup . . . . . . . . . . . . . . . . . . . . . .34, 57
save, PCBSetup, DOORS.LST. . . . . . . . . . . . . . . . . . .55
save, PCBSetup, Main Board Configuration . . . . . . . . . . .34
special. . . . . . . . . . . . . . . . . . . . . . . . . 64, 159
standard . . . . . . . . . . . . . . . . . . . . . . . . . . 159
Configure the DSZ command lines. . . . . . . . . . . . . . . . .96
CONFIGURING NETWORKS/NETMAIL . . . . . . . . . . . . . . . . . 124
CONFIGURING WITH THE ROSEMAIL SYSTEM MANAGER . . . . . . . . . .64
Connect speed. . . . . . . . . . . . . . . . . . . . .91, 100, 101
Context-sensitive help . . . . . . . . . . . . . . . . . . . . .65
Continue file scans past "old" files . . . . . . . . . . . . . 148
Control which messages in a conference shall be echoed . . . . 123
CONTROL.DAT. . . . . . . . . . . . . . . . . . . . . . . .104, 105
Conventions in Text. . . . . . . . . . . . . . . . . . . . . . 175
CONVENTIONS used in these instructions . . . . . . . . . . . . .43
COPY FILES . . . . . . . . . . . . . . . . . . . . . . .30, 45, 50
Ctrl-C key combination . . . . . . . . . . . . . . . . . . .61, 64
Ctrl-J key combination . . . . . . . . . . . . . . . . . . .60, 64
Ctrl-S key combination . . . . . . . . . . . . . . . . . . .60, 64
Ctrl-U key combination . . . . . . . . . . . . 60, 63, 84, 97, 179
Ctrl-Y key combination . . . . . . . . . . . . . . . . .60, 63, 84
Current directory. . . . . . . . . . . . . . . . . . . . . .10, 64
Current node . . . . . . . . . . . . . . . . . . . . . . . .73, 74
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 187
Cursor . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
location . . . . . . . . . . . . . . . . . . . . . . . . . . .66
movement . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Cursor highlight bar . . . . . . . . . . . . . . . . . . . . . .44
Cursor to beginning of field . . . . . . . . . . . . . . . . . .60
Cursor to end of field . . . . . . . . . . . . . . . . . . . . .60
Cursor, appearance . . . . . . . . . . . . . . . . . . . . .60, 62
Decompression program. . . . . . . . . . . . . . . . . . . . . .86
Define Transfer Protocols. . . . . . . . . . . . . . . . . . . .95
Defining your own network. . . . . . . . . . . . . . . . . . . 133
Defining your own networks . . . . . . . . . . . . . . . . . . 133
Delete all information in a field. . . . . . . . . . . . . . . .63
Delete character to left of cursor . . . . . . . . . . . . . . .60
Delete character under cursor. . . . . . . . . . . . . . . . . .60
Delete key . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Delete the ".COM" (DSZ command lines). . . . . . . . . . . . . .98
Delete the "port %2" (DSZ command lines) . . . . . . . . . . . .98
Delete the "speed %1" (DSZ command lines). . . . . . . . . . . .98
Delete the contents of the current field . . . . . . . . . . . .60
DESCRIPTION OF SUBMENUS. . . . . . . . . . . . . . . . . . . . .66
Direct mail. . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Directory names. . . . . . . . . . . . . . . . . . . . . . . . .43
Disk, swapping . . . . . . . . . . . . . . . . . . . . . . . . 115
DM (map) directory . . . . . . . . . . . . . . . . . . . . . . . 6
DM.ZIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Do not send NDX files. . . . . . . . . . . . . . . . . . . . . 175
Door dupe block. . . . . . . . . . . . . . . . . . . . . . . . 109
DOOR file. . . . . . . . . . . . . . . . . . . . . . . . . . . .54
edit . . . . . . . . . . . . . . . . . . . . . . . . .33, 54, 55
DOOR LOCATION. . . . . . . . . . . . . . . . . . . . . . . . . .45
DOOR NUMBER. . . . . . . . . . . . . . . . . . .29, 34, 45, 49, 56
Door Number for RoseMail . . . . . . . . . . . . . . . . . .32, 53
DOOR.BAT . . . . . . . . . . . . . . . . . . . . . . . . . . 7, 54
DOOR.SYS . . . . . . . . . . . . . . . . . . . . . . . . . .33, 54
DOORS file . . . . . . . . . . . . . . . . . . . . . . .34, 55, 56
example. . . . . . . . . . . . . . . . . . . . . . . . . . . .56
DOORS.LST. . . . . . . . . . . . . . . . . . . . . . . . . .32, 53
DOOR.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . .54
edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
Path to DOOR Files . . . . . . . . . . . . . . . . . . . . . .54
Security Level . . . . . . . . . . . . . . . . . . . . . . . .54
Shell. . . . . . . . . . . . . . . . . . . . . . . . . . . . .54
USER.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . .54
DOORSG file. . . . . . . . . . . . . . . . . . . . . . . . .34, 56
DOS. . . . . . . . . . . . . . . . . . . . . . . . . . . 4, 42, 48
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 188
path to DSZ. . . . . . . . . . . . . . . . . . . .48, 49, 89, 96
SET command. . . . . . . . . . . . . . . . . . . . . . . . . .93
Shell to . . . . . . . . . . . . . . . . . . . . . . . . . . 165
DOS command line . . . . . . . . . . . . . . . . . . . . . . . .86
DOS environment. . . . . . . . . . . . . . . . . . . . . . . . .93
DOS Environment variable
DSZLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
DOS ENVIRONMENT VARIABLES IN FILE PATHS. . . . . . . . . . . . .76
DOS file dates . . . . . . . . . . . . . . . . . . . . . . . . 154
DOS terminology. . . . . . . . . . . . . . . . . . . . . . . . .42
Down Arrow key . . . . . . . . . . . . . . . . . . . . . . . . .60
Download directory
local. . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Download Filename. . . . . . . . . . . . . . . . . . . . . . . .91
Download your replies. . . . . . . . . . . . . . . . . . . . . 174
Drive names. . . . . . . . . . . . . . . . . . . . . . . . . . .43
DSZ. . . . . . . . . . . . . . . . . . .37, 43, 45, 48, 88, 89, 95
case sensitivity of command lines. . . . . . . . . . . . . . .98
command lines. . . . . . . . . . . . . . . . . . . . . . . . .96
commands to estimate the time of transfer. . . . . . . . . . .98
DOS path to. . . . . . . . . . . . . . . . . . . . . .29, 48, 96
handshake commands . . . . . . . . . . . . . . . . . . . . . .98
location of. . . . . . . . . . . . . . . . . . . . . . . . . .43
set path in Transfer Protocol command lines. . . . . . . . . .96
tell RoseMail how to find. . . . . . . . . . . . . . . . . . .96
DSZ command lines. . . . . . . . . . . . . . . . . . . . . .97, 98
check. . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
edit . . . . . . . . . . . . . . . . . . . . . . . . . . . . .97
DSZ.COM. . . . . . . . . . . . . . . . . . . . . . .43, 48, 49, 97
DSZ.EXE. . . . . . . . . . . . . . . . . . . . . . .43, 48, 49, 97
DSZ.LOG. . . . . . . . . . . . . . . . . . . . . . . . . . . . .93
DSZ-compatible logs. . . . . . . . . . . . . . . . . . . . . . .93
DSZLOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92
DSZLOG Environment variable. . . . . . . . . . . . . . . . . . .93
DSZPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . .98
DTE speed. . . . . . . . . . . . . . . . . . . . . . . . . .91, 92
DUPLICATE CHECKING . . . . . . . . . . . . . . . . . . . . . . 107
Door dupe block. . . . . . . . . . . . . . . . . . . . . . . 109
RM dupe block. . . . . . . . . . . . . . . . . . . . . . . . 109
Start conference . . . . . . . . . . . . . . . . . . . . . . 110
Start RDX rebuild. . . . . . . . . . . . . . . . . . . . . . 110
Stop conference. . . . . . . . . . . . . . . . . . . . . . . 110
Duplicate checks . . . . . . . . . . . . . . . . . . . 38, 67, 158
Dynamic Size, in TPA installation. . . . . . . . . . . . . .32, 53
Echo flag. . . . . . . . . . . . . . . . . . . . . . . . .122, 123
ignore . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 189
Edit DOORS file. . . . . . . . . . . . . . . . . . . . . . .34, 55
Edit help screens. . . . . . . . . . . . . . . . . . . . . . . .70
Edit hub information . . . . . . . . . . . . . . . . . . .130, 131
Edit information in a field (edit what is already there) . . . .62
Edit information in a field (erase what is already there). . . .62
Edit the DOOR file . . . . . . . . . . . . . . . . . . . . .33, 55
Edit the DSZ command lines . . . . . . . . . . . . . . . . . . .97
Editing the Help Files . . . . . . . . . . . . . . . . . . . . .72
EMS, swapping. . . . . . . . . . . . . . . . . . . . . . . . . 115
Encrypted messages . . . . . . . . . . . . . . . . . . . . . . .22
END key. . . . . . . . . . . . . . . . . . . . . . . . . . .60, 62
End Sysop Chat Mode. . . . . . . . . . . . . . . . . . . . . . 165
ENTER key. . . . . . . . . . . . . . . . . . . . . . . . . .59, 61
Environment variable (DSZLOG). . . . . . . . . . . . . . . . . .93
Environment Variable, Transfer Protocols . . . . . . . . . . . .92
ENVIRONMENT VARIABLES IN FILE PATHS. . . . . . . . . . . . . . .76
ENVOI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Error levels . . . . . . . . . . . . . . . . . . . . . . . . . .93
ESC key. . . . . . . . . . . . . . . . . . . . . .59, 61, 165, 180
ESCaping unwanted changes. . . . . . . . . . . . . . . . . . . 179
Event. . . . . . . . . . . . . . . . . . . . . . . . . . .172, 175
EXE files. . . . . . . . . . . . . . . . . . . . . . . . . . . .50
EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
Exit to DOS. . . . . . . . . . . . . . . . . . . . . 171, 177, 178
Exit to DOS after caller . . . . . . . . . . . . . . . . . . . 165
Exit without saving your configuration . . . . . . . . . . . . .63
Expanded memory, swapping. . . . . . . . . . . . . . . . . . . 115
Extended memory, swapping. . . . . . . . . . . . . . . . . . . 115
EXTERNAL PROTOCOLS . . . . . . . . . . . . . . . . . . .29, 45, 48
F10. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
F3 . . . . . . . . . . . . . . . . . . . . . . . . . . . .165, 166
F4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
F5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
F7 . . . . . . . . . . . . . . . . . . . . . . . . . . . .165, 166
F8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
F9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
File Downloads (security level). . . . . . . . . . . . . . . . 116
File Locations . . . . . . . . . . . . . . . . . . . . . . . . .70
File Name (Add-In files) . . . . . . . . . . . . . . . . . . . 154
File name for Magazines. . . . . . . . . . . . . . . . . . . . 157
File path designation. . . . . . . . . . . . . . . . . . . . . .80
File Paths . . . . . . . . . . . . . . . . . . 35, 37, 67, 70, 176
ANSI Editor. . . . . . . . . . . . . . . . . . . . . . . . . .72
ASCII Editor . . . . . . . . . . . . . . . . . . . . . . . . .71
Edit help screens. . . . . . . . . . . . . . . . . . . . . . .70
Editing the Help Files . . . . . . . . . . . . . . . . . . . .72
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 190
environment variables. . . . . . . . . . . . . . . . . . . . .76
File Locations . . . . . . . . . . . . . . . . . . . . . . . .70
Other File Paths . . . . . . . . . . . . . . . . . . . . . . .73
PCBOARD.DAT. . . . . . . . . . . . . . . . . . . . . . . . . .74
PCBOARD.SYS. . . . . . . . . . . . . . . . . . . . . . . . . .75
Rmail Directory. . . . . . . . . . . . . . . . . . . . . . . .72
USERS.SYS. . . . . . . . . . . . . . . . . . . . . . . . . . .75
Work Directory . . . . . . . . . . . . . . . . . . . . . . . .75
File Paths for PCBOARD.DAT, PCBOARD.SYS & USERS.SYS. . . . . . .35
File transfers . . . . . . . . . . . . . . . . . . . . . . . . .48
File Uploads (security level). . . . . . . . . . . . . . . . . 116
Files
80286. . . . . . . . . . . . . . . . . . . . . . . . . . .30, 50
8088 or 8086 . . . . . . . . . . . . . . . . . . . . . . .30, 50
Add-In . . . . . . . . . . . . . . . . . . . . . . . . . .29, 47
BRDM (PCBoard) . . . . . . . . . . . . . . . . . . . . . . . .50
CNAMES.@@@ . . . . . . . . . . . . . . . . . . . . . . . . . 158
DOORS. . . . . . . . . . . . . . . . . . . . . . . . . . .34, 56
DOORSG . . . . . . . . . . . . . . . . . . . . . . . . . .34, 56
EXE. . . . . . . . . . . . . . . . . . . . . . . . . .28, 30, 50
Help text. . . . . . . . . . . . . . . . . . . . .29, 30, 47, 50
Magazine . . . . . . . . . . . . . . . . . . . . . 29-31, 47, 51
NDX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
OPT.LST. . . . . . . . . . . . . . . . . . . . . . . . . 40, 158
PCBOARD.DAT. . . . . . . . . . . . . . . . . . . . . . . . . .74
PCBOARD.SYS. . . . . . . . . . . . . . . . . . . . . . . . . .75
PWRD (PCBoard) . . . . . . . . . . . . . . . . . . . . . . . .50
RDX. . . . . . . . . . . . . . . . . . . . . . . . . . . 38, 108
RoseMail . . . . . . . . . . . . . . . . . . . . . . . . .30, 45
RoseMail menu. . . . . . . . . . . . . . . . . . . . . . .30, 50
RoseMail, Text and information . . . . . . . . . . . . . .30, 50
security-specific. . . . . . . . . . . . . . . . . . . . . . .50
text . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30
TXT. . . . . . . . . . . . . . . . . . . . . . . .30, 31, 43, 51
USERS. . . . . . . . . . . . . . . . . . . . . . . . . . . . .46
USERS.INF. . . . . . . . . . . . . . . . . . . . . . . . 46, 144
USERS.SYS. . . . . . . . . . . . . . . . . . . . . . . . . . .75
FILES=25 . . . . . . . . . . . . . . . . . . . . . . . .28, 45, 46
Finding RMAIL.DAT. . . . . . . . . . . . . . . . . . . . . . . 180
Finding your way around the menus. . . . . . . . . . . . . . . .65
Flag 16: Force this conference to be scanned. . . . . . . . . 149
Flag 17: Strip ANSI codes in incoming messages. . . . . . . . 149
Flag-setting keys: set or clear multiple flags. . . . . . . . .63
Flags on Status Line . . . . . . . . . . . . . . . . . . . . . 165
Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
GUIDED TOUR. . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 191
Help
Information boxes. . . . . . . . . . . . . . . . . . . . . . .65
text files . . . . . . . . . . . . . . . . . . . . . . . .29, 47
tickler. . . . . . . . . . . . . . . . . . . . . . . . . .65, 66
HEX code, compression program ID . . . . . . . . . . . . . . . .84
HOME key . . . . . . . . . . . . . . . . . . . . . . . . . .60, 62
Host Name. . . . . . . . . . . . . . . . . . . . . . . . . . . .39
Hotkeys, Sysop Local . . . . . . . . . . . . . . . . . . . . . 165
How RoseMail handles netmail . . . . . . . . . . . . . . . . . 122
HOW TO CONFIGURE AVAILABLE NETWORKS. . . . . . . . . . . . . . 127
HS/Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . .99
Hub sysop. . . . . . . . . . . . . . . . . . . . . . . . . . . .39
HUB.QWK. . . . . . . . . . . . . . . . . . . . . . . . . . 44, 102
HUB.REP. . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
IBM-compatible . . . . . . . . . . . . . . . . . . . . . . . . . 4
Ignore Echo Flag . . . . . . . . . . . . . . . . . . . . . . . 114
IN CASE OF DIFFICULTY. . . . . . . . . . . . . . . . . . . . . 179
Information box. . . . . . . . . . . . . . . . . . . . . . .65, 66
Insert key . . . . . . . . . . . . . . . . . . . . . . .60, 62, 96
Insert Mode. . . . . . . . . . . . . . . . . . . . . . . . . . .60
Install a "Third Party Application". . . . . . . . . . . . . . . 7
INSTALL ROSEMAIL as a Third Party Application in PCBoard . .31, 52
Installing other protocol programs . . . . . . . . . . . . . . .99
Intelec. . . . . . . . . . . . . . . . . . . . . . . . . . .1, 183
Internal protocols . . . . . . . . . . . . . . . . . . . . . . .48
Internet . . . . . . . . . . . . . . . . . . . . . . . . . .20, 21
Jump to a specified conference number. . . . . . . . . . . . . .64
KEY file . . . . . . . . . . . . . . . . . . . . . . . . . . . .22
KEYWORD. . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
KEYWORD file ROSEMAIL. . . . . . . . . . . . . . . . . . . . . .12
Keyword, in TPA installation . . . . . . . . . . . . . . . .32, 53
Leading semicolon. . . . . . . . . . . . . . . . . . . . . . . 177
Leave a Submenu. . . . . . . . . . . . . . . . . . . . . . . . .61
Left Arrow key . . . . . . . . . . . . . . . . . . . . .60, 62, 96
Limit of 101 packets . . . . . . . . . . . . . . . . . . . . . 103
Limit on expanded packet size (caller's) . . . . . . . . . . . 102
Limit on number of messages per .QWK packet. . . . . . . . . . 102
Limit on number of messages per conference . . . . . . . . . . 101
Link, PCBoard-RoseMail . . . . . . . . . . . . . . . . . . . . . 5
Links between PCBoard and RoseMail . . . . . . . . . . . . . . .51
List of editing functions. . . . . . . . . . . . . . . . . . . .61
List of Editing Keys, RoseMail System Manager. . . . . . . . . .59
Local Board Information. . . . . . . . . . . . . .37, 67, 103, 104
Board name . . . . . . . . . . . . . . . . . . . . . . . . . 104
Board telephone number . . . . . . . . . . . . . . . . . . . 105
Local directory. . . . . . . . . . . . . . . . . . . . . . . 105
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 192
Network QWK dir. . . . . . . . . . . . . . . . . . . . . . . 106
Network REP dir. . . . . . . . . . . . . . . . . . . . . . . 106
Packet name. . . . . . . . . . . . . . . . . . . . . . . . . 105
Sysop name . . . . . . . . . . . . . . . . . . . . . . . . . 105
Trashcan file. . . . . . . . . . . . . . . . . . . . . . . . 106
Local directory. . . . . . . . . . . . . . . . . . . . . . . . 105
Local user logon . . . . . . . . . . . . . . . . . . . . . . . 165
LOCALON. . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Locations of PCBOARD.DAT, PCBOARD.SYS and USERS.SYS. . . . . . .73
Lock a user out of RoseMail (or restore access to a user). . . 172
Lockout. . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Log RN files . . . . . . . . . . . . . . . . . . . . . . . . . 120
Login. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Login, DOORS.LST . . . . . . . . . . . . . . . . . . . . . . . .54
Logon. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33
Lost or stray messages . . . . . . . . . . . . . . . . . . . . 131
Magazine files . . . . . . . . . . . . . . . . .29, 31, 47, 50, 51
Magazine name. . . . . . . . . . . . . . . . . . . . . . . . . 157
Magazine subdirectory. . . . . . . . . . . . . . . . . . . . . .51
Magazines. . . . . . . . . . . . . . . . . . . . . . . . . 69, 156
File name. . . . . . . . . . . . . . . . . . . . . . . . . . 157
Magazine name. . . . . . . . . . . . . . . . . . . . . . . . 157
Security . . . . . . . . . . . . . . . . . . . . . . . . . . 157
Mail packet
control of size. . . . . . . . . . . . . . . . . . . . . . . 103
exclude NDX files. . . . . . . . . . . . . . . . . . . . . . 175
generic names for (in this guide). . . . . . . . . . . . . . .44
Local download directory . . . . . . . . . . . . . . . . . . 105
Local upload directory . . . . . . . . . . . . . . . . . . . 105
maximum expanded size. . . . . . . . . . . . . . . . . . . . 102
maximum number of messages per conference. . . . . . . . . . 101
maximum number of messages per packet. . . . . . . . . . . . 101
maximum packet size. . . . . . . . . . . . . . . . . . . . . 100
name . . . . . . . . . . . . . . . . . . . . . . . . . .103, 105
Repeat Downloads . . . . . . . . . . . . . . . . . . . . . . 103
size related to connect speed. . . . . . . . . . . . . . . . 101
Mail Waiting . . . . . . . . . . . . . . . . . . . . . . . . . 113
Main Board Configuration . . . . . . . . . . . .32, 34, 53, 55, 57
Menu Listing . . . . . . . . . . . . . . . . . . . . . . . . .55
Main menu. . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Main node. . . . . . . . . . . . . . . . . . . . . . . . . . . .41
Map files. . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
MAP files for RoseNet. . . . . . . . . . . . . . . . . . . . . . 7
Mark "Sparky" Herring. . . . . . . . . . . . . . . . . . . . . 153
Mark SysOp read. . . . . . . . . . . . . . . . . . . . . . . . 113
Max Carbon Copy. . . . . . . . . . . . . . . . . . . . . . . . 116
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 193
Max incl file (K). . . . . . . . . . . . . . . . . . . . . . . 120
Max msgs/conf. . . . . . . . . . . . . . . . . . . . . . . . . 101
Max msgs/packet. . . . . . . . . . . . . . . . . . . . . . . . 101
Max prescan (K). . . . . . . . . . . . . . . . . . . . . . . . 117
Max Work Size (K). . . . . . . . . . . . . . . . . . . . . . . 117
Maximum expanded size of the mail packet . . . . . . . . . . . 102
Maximum number of messages per conference
SIZ command (caller's) . . . . . . . . . . . . . . . . . . . 102
Maximum number of messages per packet
SIZ command (caller's) . . . . . . . . . . . . . . . . . . . 102
Maximum packet size. . . . . . . . . . . . . . . . . . . . . . 100
Memory, free . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Menu
RoseMail System Manager, main. . . . . . . . . . . . . . . . .66
Menus
Finding your way around. . . . . . . . . . . . . . . . . . . .65
Messages
dumping into the wrong conferences . . . . . . . . . . . . . .39
Modem. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
MODULES TO ADD INTO MESSAGE PACKETS: ADD-IN FILES . . . . . . 153
Monitored Messages . . . . . . . . . . . . . . . . . . . . . . .25
Move down one line . . . . . . . . . . . . . . . . . . . . . . .60
Move down one screen . . . . . . . . . . . . . . . . . . . . . .60
Move one character to the left . . . . . . . . . . . . . . . . .60
Move one character to the right. . . . . . . . . . . . . . . . .60
Move to Beginning of Field . . . . . . . . . . . . . . . . . . .62
Move to End of Field . . . . . . . . . . . . . . . . . . . . . .62
Move to next field . . . . . . . . . . . . . . . . . . . . .59, 61
Move to previous field . . . . . . . . . . . . . . . . . . .59, 61
Move up one line . . . . . . . . . . . . . . . . . . . . . . . .60
Move up one screen . . . . . . . . . . . . . . . . . . . . . . .60
Multi-node . . . . . . . . . . . . . . . . .28, 41, 42, 47, 52, 83
#-variable . . . . . . . . . . . . . . . . . . . . . . . . . .83
MULTI-NODE SYSTEMS: Checking a global RoseMail installation . .41
MULTI-NODE SYSTEMS: Configuring other nodes . . . . . . . . . .41
N switch . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
NDX files. . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Net sysop. . . . . . . . . . . . . . . . . . . . . . . . . 39, 172
USERS.INF Reset. . . . . . . . . . . . . . . . . . . . . . . 144
Net Sysop Access . . . . . . . . . . . . . . . . 39, 126, 136, 172
Net Sysop Address. . . . . . . . . . . . . . . . . . . . . . 136
Net Sysop Address. . . . . . . . . . . . . . . . . . . . . . . 136
Net Sysop Backup . . . . . . . . . . . . . . . . . . . . .113, 144
Netmail. . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Netmail QWK. . . . . . . . . . . . . . . . . . . . . . . . . . .44
Netmail REP. . . . . . . . . . . . . . . . . . . . . . . . . . .44
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 194
Network drive. . . . . . . . . . . . . . . .28, 35, 47, 52, 64, 65
Network in which to enter translations, prompt . . . . . . . . 139
Network mail
configuration. . . . . . . . . . . . . . . . . . . . . . . . .38
Network QWK dir. . . . . . . . . . . . . . . . . . . . . . . . 106
Network REP dir. . . . . . . . . . . . . . . . . . . . . . . . 106
Network software . . . . . . . . . . . . . . . . . . . . . . . .42
Network Translations . . . . . . . . . . . . . . . . .39, 126, 137
Highest in base. . . . . . . . . . . . . . . . . . . . . . . 141
Last read message. . . . . . . . . . . . . . . . . . . . . . 140
Translation. . . . . . . . . . . . . . . . . . . . . . . . . 140
Network Translations: change networks . . . . . . . . . . . . 141
NETWORK.DES. . . . . . . . . . . . . . . . . . . . . . . . . . 130
Networks/NetMail . . . . . . . . . . . . . . .38, 40, 68, 121, 172
Arranging to carry netmail . . . . . . . . . . . . . . . . . 121
CONFERENCE OWNERSHIP . . . . . . . . . . . . . . . . . . . . 134
CONFIGURING NETWORKS/NETMAIL . . . . . . . . . . . . . . . . 124
General Information. . . . . . . . . . . . . . . . . . . . . 121
How RoseMail handles netmail . . . . . . . . . . . . . . . . 122
Main Menu. . . . . . . . . . . . . . . . . . . . . . . . . . 125
NET SYSOP ACCESS . . . . . . . . . . . . . . . . . . . . . . 136
NETWORK TRANSLATIONS . . . . . . . . . . . . . . . . . . . . 137
POINTER RESETS . . . . . . . . . . . . . . . . . . . . . . . 142
RoseMail Echo Mail Features. . . . . . . . . . . . . . . . . 122
TAGLINES . . . . . . . . . . . . . . . . . . . . . . . . . . 141
USERS.INF RESET. . . . . . . . . . . . . . . . . . . . . . . 144
Networks/NetMail Main Menu
Available Networks . . . . . . . . . . . . . . . . . . . . . 125
Conference Ownership . . . . . . . . . . . . . . . . . . . . 125
Net Sysop Access . . . . . . . . . . . . . . . . . . . . . . 126
Network translations . . . . . . . . . . . . . . . . . . . . 126
Pointer Resets . . . . . . . . . . . . . . . . . . . . . . . 127
Taglines . . . . . . . . . . . . . . . . . . . . . . . . . . 126
USERS.INF Reset. . . . . . . . . . . . . . . . . . . . . . . 127
No RN encrypt. . . . . . . . . . . . . . . . . . . . . . . . . 120
Node
configuring. . . . . . . . . . . . . . . . . . . . . . . . . .64
current. . . . . . . . . . . . . . . . . . . . . . . . . . . .73
definition . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Node 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73
Node 1 directory . . . . . . . . . . . . . . . . . . . . . . . .10
Node directory . . . . . . . . . . . . . . . . . . 8, 10, 160, 181
Node number. . . . . . . . . . . . . . . . . . . . . . . . .80, 81
Node, install only one the first time. . . . . . . . . . . . . .52
Nodes
take down. . . . . . . . . . . . . . . . . . . . . . . . .31, 52
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 195
OPT.LST. . . . . . . . . . . . . . . . . . . . . . . . . . 40, 158
Option 12. . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Option 13. . . . . . . . . . . . . . . . . . . . . . . . . . . 174
Option 16 (Repeat Downloads) . . . . . . . . . . . . . . . . . 103
Option 20. . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Options. . . . . . . . . . . . . . . . . . . . . . . . . . 68, 111
Add-In Files . . . . . . . . . . . . . . . . . . . . . . . . 153
Add-in name. . . . . . . . . . . . . . . . . . . . . . . . . 154
File Downloads (security level). . . . . . . . . . . . . . . 116
File Uploads (security level). . . . . . . . . . . . . . . . 116
Mark SysOp read. . . . . . . . . . . . . . . . . . . . . . . 113
Max Carbon Copy. . . . . . . . . . . . . . . . . . . . . . . 116
Max prescan (K). . . . . . . . . . . . . . . . . . . . . . . 117
Max Work Size (K). . . . . . . . . . . . . . . . . . . . . . 117
Net Sysop Backup . . . . . . . . . . . . . . . . . . . . . . 113
Prescan Security . . . . . . . . . . . . . . . . . . . . . . 116
Remove local REP . . . . . . . . . . . . . . . . . . . . . . 113
Remove QWK file. . . . . . . . . . . . . . . . . . . . . . . 112
Remove REP file. . . . . . . . . . . . . . . . . . . . . . . 112
RoseMail Door settings for sysops. . . . . . . . . . . . . . 173
Swap to Disk . . . . . . . . . . . . . . . . . . . . . . . . 115
Swap to EMS. . . . . . . . . . . . . . . . . . . . . . . . . 115
Swap to XMS. . . . . . . . . . . . . . . . . . . . . . . . . 115
Orientation to configuring RoseMail. . . . . . . . . . . . . . .65
ORIENTATION to the task. . . . . . . . . . . . . . . . . . . . .45
Origin tagline . . . . . . . . . . . . . . . . . . . . . . . . 131
Other File Paths . . . . . . . . . . . . . . . . . . . . . . . .73
Override Prescan sec . . . . . . . . . . . . . . . . . . . . . 152
Packet name. . . . . . . . . . . . . . . . . . . . . . . .103, 105
Packet name (Networks Available) . . . . . . . . . . . . . . . 129
Page Bell. . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Password
open RoseMail Door . . . . . . . . . . . . . . . . . . . .32, 54
Path
statement. . . . . . . . . . . . . . . . . . . . . . . . . . .49
Path to DOOR Files . . . . . . . . . . . . . . . . . . . . .33, 54
Path to DSZ. . . . . . . . . . . . . . . . . . . . . . . . .48, 49
PCBDAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
PCBNODE variable . . . . . . . . . . . . . . . . . . . . . . . .81
PCBoard. . . . . . . . . . . . . . . . . . . . . . . . . . . . .42
Command prompt . . . . . . . . . . . . . . . . . . . . . . . .55
configuration for security level . . . . . . . . . . . . . . .50
version required for RoseMail. . . . . . . . . . . . . . . . . 4
PCBoard Command prompt . . . . . . . . . . . . . . . . . . . . .12
PCBoard program files, location. . . . . . . . . . . . . . . . .43
PCBoard Setup Utility. . . . . . . . . . . . . . . . . . . .34, 55
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 196
PCBoard System Manager . . . . . . . . . . .31, 34, 45, 51, 52, 57
PCBOARD.DAT. . . . . . . . . . . . . . . . . . . . . . . . .35, 74
location of. . . . . . . . . . . . . . . . . . . . . . . .36, 73
PCBOARD.SYS. . . . . . . . . . . . . . . . . . . . . . . . .35, 75
location of. . . . . . . . . . . . . . . . . . . . . . . .36, 73
PCBoard, link with RoseMail. . . . . . . . . . . . . . . . . . .51
PCBoard-RoseMail Link. . . . . . . . . . . . . . . . . . . . . . 5
PCBSetup . . . . . . . . . . . . . . . . . . . . . 32, 34, 53, 116
PCBSM. . . . . . . . . . . . . . . . . . . . . .31, 32, 45, 51, 53
Periodicals. . . . . . . . . . . . . . . . . . . . . . . . . . 156
Personal Echo Mail . . . . . . . . . . . . . . . . . . . . . . 124
PgDn key . . . . . . . . . . . . . . . . . . . . . . . . . .60, 61
PgUp key . . . . . . . . . . . . . . . . . . . . . . . . . .60, 61
PKARC. . . . . . . . . . . . . . . . . . . . . . . . . . . .37, 86
PKZIP. . . . . . . . . . . . . . . . . . . . . . . . . .37, 84, 86
Planning Your System . . . . . . . . . . . . . . . . . . . . . .57
Pointer Resets . . . . . . . . . . . . . . . . . . . .38, 127, 142
Pre-defined nets . . . . . . . . . . . . . . . . . . . . .127, 130
Pre-scan .QWK packets for net sysops . . . . . . . . . . .175, 177
Pre-scan QWK packets for net sysops. . . . . . . . . . . . . . 166
Prescan Command Line Options (ROMAIL /P method). . . . . . . . 168
Prescan Method A: "ROMAIL /P" prescan . . . . . . . . . . . . 167
Prescan Method B: TPA prescan with batch file. . . . . . . . . 170
Prescan Security . . . . . . . . . . . . . . . . . . . . .116, 152
Printer. . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Prodigy. . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
PROTOCOLS. . . . . . . . . . . . . . . . . . . . . . . . . .45, 48
external . . . . . . . . . . . . . . . . . . . . . . . . . . .48
internal . . . . . . . . . . . . . . . . . . . . . . . . .48, 88
PWRD file. . . . . . . . . . . . . . . . . . . . . . . . . . . .50
QUICK-INSTALL. . . . . . . . . . . . . . . . . . . . . . . . . .27
how to use . . . . . . . . . . . . . . . . . . . . . . . . . .27
Quick-Install, steps to perform. . . . . . . . . . . . . . . . .28
Quick-save . . . . . . . . . . . . . . . . . . . . . . . . .34, 57
QWK-format . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Range for RoseNet messages . . . . . . . . . . . . . . . . . . .20
RDX files. . . . . . . . . . . . . . . . . . . . . . . . . 38, 108
RDX rebuild. . . . . . . . . . . . . . . . . . . . . . . .110, 158
REG command. . . . . . . . . . . . . . . . . . . . . . . . . . .22
REGISTER door. . . . . . . . . . . . . . . . . . . . . . . .30, 50
Registered mail. . . . . . . . . . . . . . . . . . . . . . . . . 6
Registration of software via RoseNet . . . . . . . . . . . . . .22
Remove local REP . . . . . . . . . . . . . . . . . . . . . . . 113
Remove QWK file. . . . . . . . . . . . . . . . . . . . . . . . 112
Remove REP file. . . . . . . . . . . . . . . . . . . . . . . . 112
Repeat Downloads . . . . . . . . . . . . . . . . . . . . .101, 103
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 197
Reset message pointers to B]efore or A]fter. . . . . . . . . . 143
Restore previous information in a field. . . . . . . . . . . . .63
Restore the previous contents of the current field . . . . . . .60
Return receipts. . . . . . . . . . . . . . . . . . . . . . . . .21
Return to BBS. . . . . . . . . . . . . . . . . . . . . . . . . 165
Return to previous menu. . . . . . . . . . . . . . . . . . . . .59
Right Arrow key. . . . . . . . . . . . . . . . . . . . .60, 62, 96
RM dupe block. . . . . . . . . . . . . . . . . . . . . . . . . 109
RM RDX:<low>-<high>. . . . . . . . . . . . . . . . . . . . . . 108
RM.EXE .3, 15, 30, 35, 45, 51, 58, 64, 65, 102, 106, 107, 160, 179
RM.EXE <HUB> /I. . . . . . . . . . . . . . . . . . . . . . . . 179
RM.EXE <HUB> /S. . . . . . . . . . . . . . . . . . . . . . . . 179
RM.EXE RDX:<low>-<high>. . . . . . . . . . . . . . . . . . . . 179
RM170A.ZIP . . . . . . . . . . . . . . . . . . . . . . .30, 50, 51
RM170B.ZIP . . . . . . . . . . . . . . . . . . . . . . .30, 50, 51
RM170C.ZIP . . . . . . . . . . . . . . . . . . . . .30, 31, 50, 51
RM170D.ZIP . . . . . . . . . . . . . . . . . . . . . . . . .30, 50
RM170E.ZIP . . . . . . . . . . . . . . . . . . . . .30, 31, 50, 51
RMail Directory. . . . . . . . . . . . . . . . . . . . .35, 40, 72
RMAIL.DAT. . . . . . . . . . . .15, 40, 57-59, 64, 84, 89, 158-160
definition . . . . . . . . . . . . . . . . . . . . . . . . . .58
exit without altering. . . . . . . . . . . . . . . . . . . . .63
finding. . . . . . . . . . . . . . . . . . . . . . . . . . . 180
location . . . . . . . . . . . . . . . . . . . . . . . . . . .57
location, planning . . . . . . . . . . . . . . . . . . . . . .58
location, recommended. . . . . . . . . . . . . . . . . . . . .58
ROSEMAIL (DOOR.BAT) file command line. . . . . . . . . . . . 176
saved in current directory . . . . . . . . . . . . . . . . . .58
updating . . . . . . . . . . . . . . . . . . . . . . . . . . .58
RN encrypt . . . . . . . . . . . . . . . . . . . . . . . . . . 120
rn.<4-digit serial number>@rose.com. . . . . . . . . . . . . . .20
ROMAIL ;D;Y;G. . . . . . . . . . . . . . . . . . . . . . . . . 177
ROMAIL.EXE . . . . . . . . . . .30, 51, 58, 64, 102, 107, 175, 176
Rose Media BBS . . . . . . . . . . . . . . . . . . . 2, 6, 20, 104
Rose Media BBS REGISTER door . . . . . . . . . . . . . . . .30, 50
ROSEMAIL
/n switch. . . . . . . . . . . . . . . . . . . . . . . . . . .82
Add-In files . . . . . . . . . . . . . . . . . . . . . . . . .47
configuration, first-time. . . . . . . . . . . . . . . . .64, 65
configuration, standard, changing. . . . . . . . . . . . . . .64
description for callers (example). . . . . . . . . . . . . . .56
description in DOORS file. . . . . . . . . . . . . . . . . . .56
Door Number. . . . . . . . . . . . . . . . . . . . . .32, 49, 53
DSZ, tell RoseMail how to find . . . . . . . . . . . . . . . .96
Echo Mail Features . . . . . . . . . . . . . . . . . . . . . 122
EXE files. . . . . . . . . . . . . . . . . . . . . . .28, 47, 50
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 198
files. . . . . . . . . . . . . . . . . . . . . . . . .30, 47, 50
first installation . . . . . . . . . . . . . . . . . . . . . .52
force into immediately following logon . . . . . . . . . . . .54
Help text files. . . . . . . . . . . . . . . . . . . .29, 47, 50
Install as a Third Party Application in PCBoard. . . . . . . .52
keyword to install Third Party Application . . . . . . . . . .52
link with PCBoard. . . . . . . . . . . . . . . . . . . . . . .51
lockout. . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Magazine files . . . . . . . . . . . . . . . . . . . .47, 50, 51
menu files . . . . . . . . . . . . . . . . . . . . . . . . . .50
registered version . . . . . . . . . . . . . . . . . . .104, 181
registration . . . . . . . . . . . . . . . . . . . . . . . . .57
system requirements. . . . . . . . . . . . . . . . . . . . . . 4
Text and information files . . . . . . . . . . . . . . . . . .50
TXT files. . . . . . . . . . . . . . . . . . . . . . . . . . .51
unregistered version . . . . . . . . . . . . . . . . . .104, 181
ROSEMAIL (DOOR.BAT file) . . . . . . . . . . . . . . 31-34, 53, 55
#-variable . . . . . . . . . . . . . . . . . . . . . . . . . .82
#-variable, effect on /n switch. . . . . . . . . . . . . . . .81
example. . . . . . . . . . . . . . . . . . . . . . . . . . . .33
ROSEMAIL (DOOR.BAT) file . . . . . . . . . . . . . . . . . . . 161
command line . . . . . . . . . . . . . . . . . . . . . . . . 176
ROSEMAIL (Keyword in TPA installation) . . . . . . . . . . .52, 53
ROSEMAIL (keyword) file. . . . . . . . . . . . . . . . . . . . .74
RoseMail conference. . . . . . . . . . . . . . . . . . . . . . . 1
RoseMail directory . . . . . . . . . . . . . . . . . . . . .30, 51
RoseMail Door. . . . . . . . . . . . . . . . . . . . . . . . . .34
Option 12. . . . . . . . . . . . . . . . . . . . . . . . . . 174
Option 13. . . . . . . . . . . . . . . . . . . . . . . . . . 174
Option 16 (Repeat Downloads) . . . . . . . . . . . . . . . . 103
Option 20. . . . . . . . . . . . . . . . . . . . . . . . . . 175
password . . . . . . . . . . . . . . . . . . . . . . . . .32, 54
security level required. . . . . . . . . . . . . . . .33, 50, 54
SIZ command. . . . . . . . . . . . . . . . . . . . . . . . . 102
RoseMail Dupe indeX files. . . . . . . . . . . . . . . . . . . 108
RoseMail Echo Mail Features
Control which messages in a conference shall be echoed . . . 123
Echo flag. . . . . . . . . . . . . . . . . . . . . . . . . . 123
Personal Echo Mail . . . . . . . . . . . . . . . . . . . . . 124
Public echo mail . . . . . . . . . . . . . . . . . . . . . . 122
ROSEMAIL MAIN REFERENCE. . . . . . . . . . . . . . . . . . . . .42
GENERAL INFORMATION. . . . . . . . . . . . . . . . . . . . . .42
ROSEMAIL OPERATIONS. . . . . . . . . . . . . . . . . . . . . . 164
RoseMail Options . . . . . . . . . . . . . . . . . . . . . 38, 173
RoseMail program directory . . . . . . . . . . . . . . . . .35, 65
RoseMail program files, location . . . . . . . . . . . . . .43, 47
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 199
RoseMail System Manager. . . . .3, 15, 34, 35, 45, 49, 57, 58, 160
Board Information. . . . . . . . . . . . . . . . . . . . . . 103
COMPRESSION PROGRAMS . . . . . . . . . . . . . . . . . . . . .84
CONFERENCE OPTIMIZE. . . . . . . . . . . . . . . . . . . . . 158
Context-sensitive help . . . . . . . . . . . . . . . . . . . .65
DUPLICATE CHECKING . . . . . . . . . . . . . . . . . . .107, 108
editing functions. . . . . . . . . . . . . . . . . . . . . . .61
EXIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158
exit without saving configuration. . . . . . . . . . . . . . .63
FILE PATHS . . . . . . . . . . . . . . . . . . . . . . . . . .70
General Information. . . . . . . . . . . . . . . . . . . . . .57
Help, context-sensitive. . . . . . . . . . . . . . . . . . . .65
List of Editing Keys . . . . . . . . . . . . . . . . . . . . .59
LOCAL BOARD INFORMATION. . . . . . . . . . . . . . . . . . . 103
MAGAZINES. . . . . . . . . . . . . . . . . . . . . . . . . . 156
Main menu (illustration) . . . . . . . . . . . . . . . . . . .66
NETWORKS/NETMAIL . . . . . . . . . . . . . . . . . . . . . . 121
OPTIONS. . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Save your configuration. . . . . . . . . . . . . . . . . . . .63
TRANSFER PROTOCOLS . . . . . . . . . . . . . . . . . . . . . .88
TRANSFER RATES/LIMITS. . . . . . . . . . . . . . . . . . . . 100
USER FLAGS . . . . . . . . . . . . . . . . . . . . . . . . . 150
ROSEMAIL SYSTEM MANAGER: SUBMENUS . . . . . . . . . . . . . . .70
ROSEMAIL SYSTEM MANAGER'S MAIN MENU. . . . . . . . . . . . . . .66
RoseMail Work Directory. . . . . . . . . . . . . . . . . . . . .18
ROSEMAIL.KEY . . . .30, 31, 38, 41, 50, 51, 57, 104, 105, 121, 181
subdirectory to copy to. . . . . . . . . . . . . . . . . . . .51
ROSEMAIL, the "KEYWORD" file . . . . . . . . . . . . . . . . . .11
RoseNet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
RoseNet Archives . . . . . . . . . . . . . . . . . . . . . . . .24
RoseNet BBS system . . . . . . . . . . . . . . . . . . . . . . .20
RoseNet Central Host . . . . . . . . . . . . . . . . . . . . . .21
RoseNet Dir. . . . . . . . . . . . . . . . . . . . . . . . . . 119
RoseNet Features . . . . . . . . . . . . . . . . . . . . . . . .20
RoseNet File Information screen. . . . . . . . . . . . . . . . 118
RoseNet Host Address . . . . . . . . . . . . . . . . . . . . . .23
RoseNet Host system. . . . . . . . . . . . . . . . . . . . . . .20
RoseNet Ident. . . . . . . . . . . . . . . . . . . . . . . . . 119
RoseNet in Transit . . . . . . . . . . . . . . . . . . . . . . .25
RoseNet Information. . . . . . . . . . . . . . . . . . . . 68, 117
RoseNet Information, configuration . . . . . . . . . . . . . . 118
RoseNet Log File . . . . . . . . . . . . . . . . . . . . . . . 119
RoseNet mail . . . . . . . . . . . . . . . . . . . . . . . . . .20
RoseNet messages, range. . . . . . . . . . . . . . . . . . . . .20
RoseNet Options. . . . . . . . . . . . . . . . . . . . . . . . 120
RoseNet Pack . . . . . . . . . . . . . . . . . . . . . . . . . 121
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 200
RoseNet packing routines . . . . . . . . . . . . . . . . . . . .25
RoseNet RDX file . . . . . . . . . . . . . . . . . . . . . . . .67
RoseNet registered, routed mail. . . . . . . . . . . . 3, 6, 7, 19
RoseNet Sent . . . . . . . . . . . . . . . . . . . . . . . . . .25
ROSEREADER FOR SYSOPS. . . . . . . . . . . . . . . . . . . . 2, 20
Test Drive . . . . . . . . . . . . . . . . . . . . . . . . . . 2
RoseReader Lite for Sysops . . . . . . . . . . . . . . . . . . .20
RoseReader Serial Number . . . . . . . . . . . . . . . . . . . .20
Routed mail. . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Routing information. . . . . . . . . . . . . . . . . . . . . . . 6
Save your RoseMail configuration . . . . . . . . . . . . . . . .63
SAVING RMAIL.DAT INFORMATION . . . . . . . . . . . . . . . . . 158
Scan date and time . . . . . . . . . . . . . . . . . . . . . . 143
Scramble code. . . . . . . . . . . . . . . . . . . . . . . . . .21
Screen on/off. . . . . . . . . . . . . . . . . . . . . . . . . 165
Screen simulations . . . . . . . . . . . . . . . . . . .44, 66, 84
Scroll Screen. . . . . . . . . . . . . . . . . . . . . . . . . .61
Security (Add-In files). . . . . . . . . . . . . . . . . . . . 155
SECURITY LEVEL . . . . . . . . . . . . . . . . . . . . .29, 30, 49
minimum to use RoseMail. . . . . . . . . . . . . . . .33, 45, 50
open RoseMail Door . . . . . . . . . . . . . . . . . . . . . .54
Security level for Magazines . . . . . . . . . . . . . . . . . 157
Security-specific menu files . . . . . . . . . . . . . . . . . .50
Select a submenu . . . . . . . . . . . . . . . . . . . . . .59, 61
Semicolon, leading . . . . . . . . . . . . . . . . . . . . . . 177
SERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . 153
SERVICES file (for Add-In files) . . . . . . . . . . . . . . . 155
Set flags for a range of conferences . . . . . . . . . . . . . .64
Set Mail Waiting . . . . . . . . . . . . . . . . . . . . . . . 113
Set multiple flags . . . . . . . . . . . . . . . . . . . . . . .63
Settings to use if your hub has RoseMail . . . . . . . . . . . 173
SETUP.170. . . . . . . . . . . . . . . . . . . . . . . . . . . .28
Shared data files. . . . . . . . . . . . . . . . . . . . . . . . 9
Shell
DOORS.LST. . . . . . . . . . . . . . . . . . . . . . . . .33, 54
Shell Door, PCBoard 14.5a. . . . . . . . . . . . . . . . . .33, 54
Shell to Dos . . . . . . . . . . . . . . . . . . . . . . . . . 165
Shift-TAB key. . . . . . . . . . . . . . . . . . . .44, 59, 61, 84
Single-node. . . . . . . . . . . . . . . . . . . . . . .40, 73, 83
#-variable . . . . . . . . . . . . . . . . . . . . . . . . . .83
SIZ command. . . . . . . . . . . . . . . . . . . . . . . . . . 102
Smartnet . . . . . . . . . . . . . . . . . . . . . . . . . .1, 183
Special care needed with numbers . . . . . . . . . . . . . . . 124
SPECIAL CONFIGURATIONS (multi-node systems only) . . . . . . . .45
SPECIAL CONFIGURATIONS FOR INDIVIDUAL NODES. . . . . . . . . . 159
Special RoseMail configurations for individual nodes . . . . . .16
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 201
Start conference (Duplicate checking). . . . . . . . . . . . . 110
Static Size, in TPA installation . . . . . . . . . . . . . .32, 53
Status Line Flags. . . . . . . . . . . . . . . . . . . . . . . 165
Step numbers in Quick-Install. . . . . . . . . . . . . . . . . .28
Steps, installation. . . . . . . . . . . . . . . . . . . . . . .45
Stop conference (Duplicate checking) . . . . . . . . . . . . . 110
Stray messages . . . . . . . . . . . . . . . . . . . . . . . . 131
Subdirectories . . . . . . . . . . . . . . . . . . .28, 43, 45, 47
Swap options . . . . . . . . . . . . . . . . . . . . . . . . . 115
Swap to Disk . . . . . . . . . . . . . . . . . . . . . . . . . 115
Swap to EMS. . . . . . . . . . . . . . . . . . . . . . . . . . 115
Swap to XMS. . . . . . . . . . . . . . . . . . . . . . . . . . 115
Swapping Techniques. . . . . . . . . . . . . . . . . . . . . . 115
Symbol . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66
Symbols. . . . . . . . . . . . . . . . . . . . . . . . . . . . .44
Sysop Chat Mode. . . . . . . . . . . . . . . . . . . . . . . . 165
Sysop Local Hotkeys. . . . . . . . . . . . . . . . . . . . . . 165
Sysop Module pseudo-conferences. . . . . . . . . . . . . . . . .24
Sysop name . . . . . . . . . . . . . . . . . . . . . . . . 103-105
Sysop RoseNet. . . . . . . . . . . . . . . . . . . . . . . . . .24
Sysop, brand-new . . . . . . . . . . . . . . . . . . . . . . . .42
SYSOP@<packet name>. . . . . . . . . . . . . . . . . . . . . . .20
SYSTEM CONFIGURATION . . . . . . . . . . . . . . . . . .28, 45, 46
System environment variables . . . . . . . . . . . . . . . . . .76
SYSTEM REQUIREMENTS FOR RUNNING ROSEMAIL . . . . . . . . . . . . 4
TAB key. . . . . . . . . . . . . . . . . . . . . . .44, 59, 61, 84
Taglines . . . . . . . . . . . . . . . . . . . . . . . . .126, 141
Terminology used in this guide . . . . . . . . . . . . . . . . .44
Text editor. . . . . . . . . . . . . . . . . . . . . . .33, 34, 55
edit ASCII help files. . . . . . . . . . . . . . . . . . . . .35
edit DOOR.BAT file . . . . . . . . . . . . . . . . . . . . . .55
Text files . . . . . . . . . . . . . . . . . . . . . . . . . . .50
information. . . . . . . . . . . . . . . . . . . . . . . . . .50
TEXT subdirectory. . . . . . . . . . . . . . . . . .29, 31, 47, 51
TEXT subdirectory name . . . . . . . . . . . . . . . . . . . . .43
Third Party Application. . . . . . . . . . . .3, 7, 31, 32, 52, 53
Dynamic Size . . . . . . . . . . . . . . . . . . . . . . . . .53
Keyword. . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Static Size. . . . . . . . . . . . . . . . . . . . . . . . . .53
Version. . . . . . . . . . . . . . . . . . . . . . . . . . . .53
Tickler help . . . . . . . . . . . . . . . . . . . . . . . .65, 66
Toggle exit to DOS after caller. . . . . . . . . . . . . . . . 165
Toggle Insert Mode . . . . . . . . . . . . . . . . . . . . .60, 62
Toggle Page Bell . . . . . . . . . . . . . . . . . . . . . . . 165
Toggle printer . . . . . . . . . . . . . . . . . . . . . . . . 165
Toggle screen on/off . . . . . . . . . . . . . . . . . . . . . 165
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 202
Toggle sysop next. . . . . . . . . . . . . . . . . . . . . . . 165
Tour of RoseMail operations. . . . . . . . . . . . . . . . . . .13
TPA method, Batch File To Pre-scan QWK Packets . . . . . . . . 171
Transfer Protocol command lines
point to DSZ . . . . . . . . . . . . . . . . . . . . . . . . .96
Transfer Protocols . . . . . . . . . . . . . . . . .37, 67, 88, 89
alterations you may make to command lines. . . . . . . . . . .98
Bat. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
Checklist for configuring. . . . . . . . . . . . . . . . . . .95
com port in use. . . . . . . . . . . . . . . . . . . . . .91, 92
command line examples for DSZ. . . . . . . . . . . . . . . . .97
command lines. . . . . . . . . . . . . . . . . . . . .49, 88, 89
configuration. . . . . . . . . . . . . . . . . . . . . . . . .49
connect speed. . . . . . . . . . . . . . . . . . . . . . . . .92
Define . . . . . . . . . . . . . . . . . . . . . . . . . . . .95
Download program . . . . . . . . . . . . . . . . . . . . . . .91
Download program, bi-directional protocols . . . . . . . . . .91
Download program, com port in use. . . . . . . . . . . . . . .91
Download program, computer-to-modem speed. . . . . . . . . . .91
Download program, connect speed. . . . . . . . . . . . . . . .91
Download program, DTE speed. . . . . . . . . . . . . . . . . .91
Download program, edit command lines . . . . . . . . . . . . .97
Download program, filename . . . . . . . . . . . . . . . . . .91
DSZ command lines. . . . . . . . . . . . . . . . . . . . .92, 98
Environment variable . . . . . . . . . . . . . . . . . . . . .92
Err. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
General Information. . . . . . . . . . . . . . . . . . . . . .88
Let. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .90
Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . .91
screens. . . . . . . . . . . . . . . . . . . . . . . . . .89, 90
Upload program . . . . . . . . . . . . . . . . . . . . . . . .92
Upload program, com port in use. . . . . . . . . . . . . . . .92
Upload program, computer-to-modem speed. . . . . . . . . . . .92
Upload program, connect speed. . . . . . . . . . . . . . . . .92
Upload program, DTE speed. . . . . . . . . . . . . . . . . . .92
Upload program, filename . . . . . . . . . . . . . . . . . . .92
Transfer Rate. . . . . . . . . . . . . . . . . . . . . . . . . 101
Transfer Rates/Limits. . . . . . . . . . . . . . . . . 37, 67, 100
Max msgs/packet. . . . . . . . . . . . . . . . . . . . . . . 101
Transfer Rate. . . . . . . . . . . . . . . . . . . . . . . . 101
Translation. . . . . . . . . . . . . . . . . . . . . . . . . . 140
Translation codes for network mail . . . . . . . . . . . . . . 140
Trashcan file. . . . . . . . . . . . . . . . . . . . . . . . . 106
disable checking . . . . . . . . . . . . . . . . . . . . . . 106
Trashcan file, edit. . . . . . . . . . . . . . . . . . . . . . 107
True Ymodem. . . . . . . . . . . . . . . . . . . . . . . . . . .94
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 203
TXT files. . . . . . . . . . . . . . . . . . . . . .31, 43, 50, 51
U'NI-net . . . . . . . . . . . . . . . . . . . . . . . . . .1, 183
Undo key . . . . . . . . . . . . . . . . . . . . . . . . . . . .63
Undo procedure . . . . . . . . . . . . . . . . . . . . . . . . .63
Unpredictable results. . . . . . . . . . . . . . . . . . . 39, 136
Untagged messages. . . . . . . . . . . . . . . . . . . . . . . 131
Up Arrow key . . . . . . . . . . . . . . . . . . . . . . . . . .60
UPGRADING your ROSEMAIL. . . . . . . . . . . . . . . . . . . . 181
Upload directory
local. . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Upload Filename. . . . . . . . . . . . . . . . . . . . . . . . .92
Use current date/time. . . . . . . . . . . . . . . . . . . . . 174
UseNet . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
User allowed in door . . . . . . . . . . . . . . . . . . . . . 152
User allowed RoseNet . . . . . . . . . . . . . . . . . . . . . 152
User Check . . . . . . . . . . . . . . . . . . . . . . . . . . .21
User Flags . . . . . . . . . . . . . . . . . . . . 40, 63, 68, 150
Deny netmail access in this conference . . . . . . . . . . . 152
Deny the user access to this conference. . . . . . . . . . . 152
Scan for personal messages . . . . . . . . . . . . . . . . . 151
Scan for public messages . . . . . . . . . . . . . . . . . . 152
User gets SysOp status in this conference. . . . . . . . . . 152
User Info File Maintenance . . . . . . . . . . . . . . . . .31, 52
USER.SYS . . . . . . . . . . . . . . . . . . . . . . . . . .33, 54
USERS file . . . . . . . . . . . . . . . . . . . . . . . . . 7, 46
USERS.INF. . . . . . . . . . . . . . . . . .7, 32, 38, 46, 52, 144
Reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
USERS.INF file
modify . . . . . . . . . . . . . . . . . . . . . . . . . . . .53
USERS.INF Reset. . . . . . . . . . . . . . . . . . . . . .127, 144
USERS.SYS. . . . . . . . . . . . . . . . . . . 7, 35, 75, 171, 178
location of. . . . . . . . . . . . . . . . . . . . . . . .36, 73
Version number in TPA installation . . . . . . . . . . . . . . .53
Version, in TPA installation . . . . . . . . . . . . . . . .32, 53
Vic Kass . . . . . . . . . . . . . . . . . . . . . . . . . . . .23
W (Write) command. . . . . . . . . . . . . . . . . . . . . . . . 6
WHATSNEW.200 . . . . . . . . . . . . . . . . . . . . . . . . . .19
Work Directory . . . . . . . . . . . . . . . . . . . . .18, 37, 75
Xmodem . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
XModem protocol. Checksum error control with 128 byte packets .94
XModem protocol. CRC error control with 128 byte packets. . . .94
Xmodem-1K. . . . . . . . . . . . . . . . . . . . . . . . . . . .99
XModem-1K protocol. CRC error control with 1024 byte packets. .94
XModem-G protocol. CRC error detection with 1024 byte packets .94
XMS, swapping. . . . . . . . . . . . . . . . . . . . . . . . . 115
Ymodem . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
Copyright (C) 1992-93 by Rose Media Inc.
Sysop's Guide to RoseMail Page 204
YModem protocol. CRC error control with 1024 byte packets . . .94
Ymodem-G . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
YModem-G protocol. CRC error detection with 1024 byte packets .95
Zmodem . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88
ZModem protocol. CRC error control and batch file transfers . .95
Zmodem-MobyTurbo . . . . . . . . . . . . . . . . . . . . . . . .88
Copyright (C) 1992-93 by Rose Media Inc.